-
Suggestion
-
Resolution: Timed out
-
4
-
Summary
When setting the workflow condition using the "Assignee" field, you can only set the individual assignee as a value but cannot reference the user group or project role.
Use case scenario
The customer wants to make sure that a specific user is in the Assignee field before the ticket can be transitioned to the next status.
But because the condition for Assignee fields does not have a "Is a member of" or "is not a member of" setting, they can't base the condition on a user group or project role.
And each assignee has to be entered as a separate condition.
Problem
When new team members are onboarded, the transitions need to be modified. This is not sustainable and being able to use a user group or project role would be much easier.
- relates to
-
JRACLOUD-9311 Assignable user restricted upon workflow steps
- Closed
-
JRACLOUD-72131 Ability to use the property jira.permission.assignable.projectrole in transitions
- Closed
Hi everyone,
Thank you for bringing this suggestion to our attention. As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritise and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.
Unfortunately, as a result of inactivity for an extended period of time, this suggestion didn’t make it to the roadmap and we are closing it.
While this issue has been closed, our Product Managers continue to look at requests on jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.
Thank you again for providing valuable feedback to our team - Jira Cloud Product Management