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

Notifying user that condition not met for transtion

Ivar Anneljas

Hi!

Is there anyone out there who knows a simple solution for the following.

Main issue has subtasks, if conditions are not met(sub-tasks have to be closed) transition button is not displayed.

What we would like to achieve is to have the button visible, but if users clicks on it a error message is displayed with a notification that they need to close/complete sub-tasks before transiting to next status.

smile

Ivar

Accepted answers

Jobin Kuruvilla [Adaptavist]

You can write a workflow validator plugin to check for open subtasks. A validator shows the worklfow button but throws the error if the validation fails. Looks like that is what you are after!

All comments

Joe Pitt

You're looking at modifying the basic JIRA code. The absence of the transaction tells the users the conditions aren't met. They would have to look at the issue to see the button and get the error. This is a training issue. Trying to fix it with a code hack will only bring you grief in the long run.

Peter Bengov

Hey Ivar,

if we try to simplify this then look at issues a bit differently: Conditions are there to prevent clutter and non relevant transitions.

If you want to display a message of missing component/fields/sub-tasks then this should be done as a validator, which comes with this ability on notifying users.

I know this might sound a bit strange, but this is a preferred solution to your problem.

Jobin Kuruvilla [Adaptavist]

You can write a workflow validator plugin to check for open subtasks. A validator shows the worklfow button but throws the error if the validation fails. Looks like that is what you are after!

SimonH_f8351i

I too would like this functionality. Every condition I add is something that prevents the validation button from appearing with absolution no explanation why. It leads to confusion and wasted time, and is poor design: an IT system should help the user understand how it works, not baffle them.

The result of this poor design is that we end up not putting in Conditions for certain things, because it causes such confusion.

SimonH_f8351i

The problem is that not all Conditions checks are also available as Validator checks.

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-administration