Avatar
Chance Callahan Burgess

Attività totali
27
Attività recente
Membro dal
Seguiti
0
Seguito da
0
Badge

Panoramica attività

Panoramica attività

Ultima attività di Chance Callahan Burgess
Avatar
Chance Callahan Burgess ha commentato,
  1. Community
  2. Product Feedback
  3. Assign on Status Change as Routing Mechanism

Up-voting this feature request. Would be very helpful!

Avatar
Chance Callahan Burgess ha commentato,
Avatar
Chance Callahan Burgess ha commentato,
  1. Community
  2. Product Feedback
  3. Automation of the Task Status

Agreed - this would be an awesome feature!

Avatar
Chance Callahan Burgess ha commentato,
  1. Community
  2. Product Feedback
  3. [Status: Not planned] Tasks dependency setup should not be locked base on Task Status

I noticed this too while I was iterating a project template that we use. I had to change the parent tasks to an active status before it would let me assign dependencies. Looking forward hearing a r...

Avatar
Chance Callahan Burgess ha commentato,
  1. Community
  2. Product Feedback
  3. Workflow suggestion to allow specified folder allocation on assignment of workflow

I agree with Zilvinas. It would be awesome for Admins to associate certain Workflows and/or their statuses with specific folders. This would help ensure organizational continuity when a user change...

Avatar
Chance Callahan Burgess ha creato un post,
  1. Community
  2. Product Feedback

It would be awesome for Admins to associate certain Workflows and/or their statuses with specific folders. This would help ensure organizational continuity when a user changes the workflow of a tas...

Avatar
Chance Callahan Burgess ha commentato,
  1. Community
  2. Product Feedback
  3. Request Forms: Add task to folder dropdown

The ability for a user to search for and select an associated folder or project directly in the request form (before submitting) would be an incredibly valuable feature that would solve a lot of he...

Avatar
Chance Callahan Burgess ha commentato,
  1. Community
  2. Product Feedback
  3. Preserve Tagging After Project/Task Duplication

I cannot believe that this hasn't been prioritized. This is critical for us to manage tasks effectively with multiple cross-functional stakeholders. When will this be on the road map?