I want to ensure that certain practices should be followed by the team while creating the JIRA issue. While the issue creator is clicking the create button, In case those practices are not followed, then I want a pop-up message to be displayed to the user and the issue shouldn't be created until the required practice is not validated on the click of create button.
I am able to set the trigger and condition. How shall I set the action to show pup-up message being a Project Administrator?
Let me share my exact need.
As the best practice, while creating the JIRA Issue, I have to ensure that the priority is set and a default assignee is set as per the activity type. For example: If the activity description suggest it's a backend activity then it should be assigned to my backend Lead. Similarly, it it's a Frontend activity, then it should be assigned to Frontend Lead, If QA activity, then QA Lead, if DevOps activity then DevOps Lead and so on. Basically ensuring that it is not unassigned while creating.
Hence, while creating the ticket, while clicking the create button, I have to validate if both priority and assignee fiends are not left empty. If it's left empty, I need to hold the create process and help the ticket created on the missed info on the issue through a popup message.
Look, first, we need to break down the problem you're presenting into two parts:
From what I see, this is what you're trying to achieve.
To accomplish the first point, I suggest adding a rule within the workflows you're using. The rule will work as follows:
Jira will verify if these fields are filled. If it returns false, the workflow will not allow the transition to proceed.
Automation rule in the workflow:
To achieve the second point, you need to go to the automation section and create the following rule:
This condition will need to be repeated for every issue type you have. For example, if you have 10 different issue types such as QA, Service Requests, Incidents, Bugs, etc., you’ll have to create a condition for each one, essentially nesting multiple IF-ELSE statements.
This is not the best practice, but Jira’s automation has limitations when it comes to handling complex and dynamic queries.
Automation rules in Jira:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Gustavo Ezequiel Szemruck for the detailed response. It helps. The only anticipation I want to highlight here is, I want to check the validation of Assignee and priority at the time of issue creation itself and in case any of the validation fails, I want to notify the user and don't want to create the issue (or ticket) until all the validations are satisfied.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Automation rules run after some event has happened. They cannot halt processing to show a dialog / pop-up screen.
What are the "certain practices" to be followed?
If there are required fields, you could either make them required for all issues or add a validator or transition screen to the workflow. For more advanced needs, see marketplace addons.
https://support.atlassian.com/jira-cloud-administration/docs/configure-advanced-issue-workflows/
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, @shantanu behera
To display a pop-up message or an error the way you're looking for, Jira does not support this natively.
If you're looking for more flexibility when creating issues, I recommend using extensions like ScriptRunner, which allows you to display messages through an event listener.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.