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; } } }

Automation flow just for Sub-task. Is it possible?

unknown

Could you help me to undertand the way of creating the spesific automation flow for some kind of issue?

Let's say I want to create the automation JUST for Sub-task. The condition are following:

1. Just for the Sub-task: unable the transition from TO DO ---> IN PROGRESS if estimation input is empty. Is it possible create this kind of automation for one kind of issue? I can't find the way to separate automation depending on issue type.

2. Could you help me to understand how to add some error message for the automation like pop-up or something like that: "You can't move the Sub-task to IN PROGRESS with no estimation info in the spesific field, please add the estimation to move the issue" it is the example. Right now the issue just come back from the IN Progress to the TO DO status, but I want to inform about the reason of this flow, to get user understand why is it so.

Accepted answers

Harrison Ponce

Hi @[deleted]!

You probably want something like the screenshot below, where it triggers on transition and validates through issue fields conditions that it is a sub-task and blank estimate before changing the status back. You can also add a comment to the issue and tag the reporter, assignee, or person who initiated the transition with a note about the estimates being blank.

Adding a pop-up notification can be a little tricky. Usually that is done when you have a workflow validator (or a marketplace app / Forge custom app). This could work, but would apply to all issue types that share the same workflow (likely your sub-task shares same as higher issue types). If you did piece off your sub-tasks into a different workflow (maybe a simpler one) then you could absolutely add a workflow validator for the value of the estimates field and then it would only be for the sub-tasks. Those do allow you to put some custom message and they show up as a temporary pop-up in the lower left corner of the screen.

Hope this is helpful!

Trudy P Claspill

Hello @[deleted]

Concerning your first question, you cannot use Automation Rules to prevent the transitioning of an issue from one status to another. Automation Rules can only react to completed events. An Automation Rule could recognize that the sub-task had been transitioned to In Progress, check if the estimation field is empty, and then automatically transition it back to To Do.

To prevent the transition you would have to implement that customization through Workflow customization by adding a Validator to the transition. The specific steps depend on whether you are working with a Team Managed project or a Company Managed project. In either case, you can have different workflows for each issue type in your project, so it is possible to implement this.

Related to your second question, a pop-up could be associated with this customization only if the issues are in a Company Managed project. If the issues are in a Team Managed project, that does not support showing an error message with a Validator.

All comments

Harrison Ponce

Hi @[deleted]!

Hope this is helpful!

Trudy P Claspill

Hello @[deleted]

unknown

@Trudy P Claspill your response is helpful, thanks. I don't realize the differences between preventing the transition via workflow and automation as the way of "completed events".

unknown

@Harrison Ponce thanks, I've missed the issue fields conditions, it helps a lot)

"You can also add a comment to the issue and tag the reporter, assignee, or person who initiated the transition with a note about the estimates being blank." it was also helpful.

I appreciate your reply, thanks!

Harrison Ponce

Glad I could help!

I Gotchu I Got You GIF by Max

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