Product ideas | Community
Skip to main content

10000 Ideas

MoniqueEvans
MoniqueEvansNew Participant

Tie Issue Status to Converted Projects In PerpetuityNew

Description - When an issue is resolved by another object, the status and progress are locked and only updated via the resolvable. Unfortunately, if you were to mark the resolving/converted project as Dead, the issue is also Dead and will no longer update regardless of the updates that continue to happen on the project. For example, you convert an issue to a project, work starts and the team thinks it's a duplicate ask so they mark the project as Dead. A meeting happens, and you learn that it is very similar to an existing project but unique enough to continue so you update the project's status to Current. Meanwhile, the Issue will continue to say Dead and you cannot update the status because it is locked by the resolving project. I would like for the issue to continue monitoring the resolving project and update the status if the project reopens (from being Complete or Dead).   Why is this feature important to you - If the project management team isn't aware of this you have issues telling a completely different story than what is happening which can skew metrics. This is especially damaging if you have one person reporting from the issues and another person reporting from the projects. We always want our metrics and reports to be accurate since those are influencing business decisions.   How would you like the feature to work - The issue's status would update from Dead to In Progress if the resolving project status changed from Dead back to Current or Planning.   Current Behaviour - Currently the only workaround is to manually remove the resolve by information, save the issue, and then add the resolve by information back since you cannot update the issue's status individually while a resolvable is listed.

JanineDiNew Participant

Ability to bulk remove unassigned roles from assignment fieldNew

Description - If I have a project template that has tasks with several roles assigned, and then determine that I don't need to fill each role, I'd like to have a way to bulk remove unassigned roles from task assignments. Why is this feature important to you - I noticed one time when I had it assigned to one UX Designer (name Jeri Bailer), but had a second UX Designer role assigned to the same task but left UNassigned.  It then was not calculating Jeri's time off in the project timeline.  It was assuming we would assign someone else who could work through her time off.  Therefore this affected the project's overall timeframe. How would you like the feature to work - If I remove a person from an assigned role or leave a role unassigned, I'd like to have an option to remove unassigned roles from all assignments. Current Behaviour - See Why above. Also see screenshots of the example with the unassigned role left in and it's affect on the timeline versus removed. Jeri has PTO scheduled in her Time Off field from Feb 26 to Mar 4. You'll see one attachment shows the work being completed through that task b/c there is an unassigned UX Designer to the task.  The other attachment will show you the change in timeline when I remove the unassigned role and it then calculates in Jeri's time off.  It not a big deal to remove one or two roles, but sometimes it's every task in the project and that is tedious.