I am trying to allow the current assignee to close a subtask. I have that added as an explicit permission on my project. You cannot differentiate between an issue and subtask, from what I see in permissions. I DO have certain transitions on the parent issue limited by user group....but subtasks I thought were distinct entities on their own. subtasks in this case don't have any transitions. What am I missing in my setup?
There's two layers to it here.
First, the permissions - you might have "close" permission, but that doesn't necessarily mean you can or can't close. It's more of a flag than anything else.
Secondly, there's the workflow. As you've hinted, you can put conditions on the workflow. Like "user must have the close permission"
The trick for your case is knowing that you can tell Jira to use different workflows by issue type. So you can say things like "for bugs, a user must have close permission, but for sub-tasks, they must be in group X"
Well, I sort of got that far. the subtask workflow is a default workflow (whatever came in basic jira) handled by our baseline jira admins, and I don't think I can even see that to know what it contains. I wouldn't think it would be too exclusive, but I could be wrong. I know I don't exclude anything in my setup. (logically who else would close their own subtask right?)
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs