You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We need to be able to report on issues based on role. I must be missing something obvious here because I can't seem to find a way to do that.
What is the JQL for instance that returns all the Defects that are assigned to users in the Developers role?
Here's another thought - not sure if it's what you want, but trying to help.
Set the conditions of a project workflow transition to filter issues based on Roles. The person in a specific role is the only one who can see the transition. Use a workflow post function to apply a specific label or set a custom field value. Now, the issue is tagged by the Role of the person who transitioned it. That tag (label/field) can be used as a condition to other workflow transitions and/or in a filter.
Because a workflow transition can end on the same status on which it began (loop transition), you can use a transition just to apply labels or set field values without actually transitioning the issue. And once you've tagged them, other workflow conditions can make transitions available that weren't visible to untagged issues. So, for example, a loop transition could apply a label "hardware" and a condition could check for that label, allowing only properly tagged issues to transition.
Another approach might be to create a custom user picker field that you assign based on some workflow condition. It might start out as a copy of the Assignee field, but then get modified in a subsequent workflow transition. With that custom user picker field limited to only the people that you want to have in it, you can build reports and filters using that field and know that it won't have "just anybody" in it.
Hope this helps. And, yes, it would be better if Jira had the required logic to do this without such a circuitous workaround.
You can checkout the Scription JQL function support in SR. I've never tried it but maybe the jiraUserPropertyEquals function will work. There's a note in the doc that only admins can use it though...
Thanks, but that would negate one of the advantages of using roles: that they can be maintained by a Project Administrator. Groups require JIRA admin access.
Bizarre JIRA does not have this function OOB, especially because of their push for the Project Administrators to take some of the load off of the JIRA Administrators.