nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Condition to block/allow subtask transition based on parent issue type and user role?

Michael Arndt_smtys6

Is there a way to block a subtask transition based on both the parent issue type and the user role?

For example

If issue type is a subtask and parent issue type is STORY then disallow transition of subtasks from In Progress to DONE unless user has Project Role XYZ

If issue type is a subtask and parent issue type is TASK then allow transition of subtasks from In Progress to DONE if user has Project Role ABC

Edit: Had to fix my example.

Accepted answers

All comments

Kian Stack Mumo Systems

You need to install JMWE to Jira Cloud in order to accomplish this. It cannot be done through the standard functionality.

You'll want to use the new condition "Linked Issues Condition (JMWE app)". You'll configure it like this:

Screen Shot 2019-07-02 at 6.07.00 AM.png

You would then need to add a nested condition to ensure the user is in the correct user role.

You'd then build the second set of conditions for the task/other project role. In the end, it would look something like this:

Screen Shot 2019-07-02 at 8.41.56 AM.png

You would click on the fork to build the nested conditions.

What this screenshot shows is that you need to meet 1 of the two conditions, but for each condition you need to meet all the nested conditions. So, a parent ticket of type "Story" you must be a developer to transition. OR your parent could be a task in which case you need to part of the service desk team.

Hope this helps!

Kian

EDIT: Updated Screenshots to reflect correct condition configuration.

Michael Arndt_smtys6

In my case I want to set conditions on the subtask so wouldn't it be

Issue Link Type is a subtask of 

Issue Type Story

Kian Stack Mumo Systems

No, because the link is checking based on the relationship to the current ticket. This would be a set of conditions on the subtask workflow.

Essentially, you are saying "If my parent is a story, you must be in project role X to transition me".

Does that make sense?

Michael Arndt_smtys6

I think my example in my original post may have been wrong. Here's what I meant to say

If issue type is a subtask and parent issue type is STORY then disallow transition of subtasks from In Progress to DONE unless user has Project Role XYZ

If issue type is a subtask and parent issue type is TASK then allow transition of subtasks from In Progress to DONE if user has Project Role ABC

Does that change this?

Oliver Siebenmarck {Polymetis Apps}

Hi Michael,

While Kian's approach with JMWE should work, it'd like to show off an alternative app, called Cloud Workflows, that you could use. It allows you to add conditions and validators based on Jira Expressions.

In case there are more issue types than just the sub-task in your workflow, you'll want to test for that first, which looks like this:

issue.issueType.name == "Sub-task"

Additionally, you want to ensure that the parent of the issue has a specific type, which can simply be added with the following:

issue.issueType.name == "Sub-task" 
&& issue.parent.issueType.name == "Story"

So, you would create a Cloud Workflows custom condition with the above Jira Expression and combine that with a condition that checks a user's project role and you're done.

Hope that helps!

Full disclosure: I work for the Vendor who created Cloud Workflows. Let me know if you need any help getting started.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud