I wan to to prevent the issue to be created or edited if flagged with no reason informed

[Adilson Simões]

I would like to prevent issues to be edited or created when flagged as impediment and the user don´t inform a reason for that impediment. The first option that came to my mind was an automation. But there is no action that can prevent the creation of the issue nether a popup message to inform that rule to the person that is editing/creating the issue.

It also could be solved by a field required based on the value of another field.

It there any other option that I could try to achieve similar behaviour? 

[Ted Nieblas]

@Adilson Simões - there are a number of ways to accomplish this depending on your specific use case. Can you give me a bit more context regarding "edited or created when flagged as impediment"?

• Is this a field on the ticket?
• Is this an issue type?
• Is it a linked issue of type "blocks"?

The most straightforward way is to make the "reason for impediment" field required for the issue type. If you want it conditional based on the value of another field you may want to look at using a JSM or JWM form to have more control over fields at time of creation. Preventing the same behavior on editing is a bit more complex. 

Before diving further, please give me more details on what you are trying to do.

[Adilson Simões]

Hi @Ted Nieblas , thank you for your answer.

What I really want is that all flagged issues must have a "reason for impediment". If the user does not provide the "reason for impediment", the issue cannot be saved if flagged.

[Ted Nieblas]

Hi @Adilson Simões , I understand the solution you are trying to implement, I was trying to find out what problem you were trying to solve.

Preventing an issue from being created unless a required field is fairly simple to do. Preventing an issue from being saved while editing is a bit more complex. The first can be achieved by making a field mandatory in certain contexts. The latter will likely require an automation to notify the user if a condition exists. 

In my experience, it is better to use the features of Jira as they were intended to be used. In this case I would use a Linked Issue of types "blocks" or create a new one of type "impedes/is impeded by" and use automations to perform actions based on those conditions.

[Ted Nieblas]

Hi @Adilson Simões

I have achieved something similar to what you are describing with the following automation rule.

This rule prompts the user for input ("reason for impediment") and inserts the value into a field and then changes the field values of other fields as well as those in related issues that meet my criteria. This automation is manually triggered via the "Actions" menu of the issue which is right next to the issue status field in the default view.

It's simpler than requiring the user to select a field ("is impeded") and then enforce rules before saving the issue, which, as I have explained, is rather difficult.

Give it a try and let me know if I can help you further.