Maciej Dudziak _Forgappify_ Atlassian Partner

I don't think it's possible ootb. However with Jira expression-based condition you could write following: user.groups.includes('X') && issue.assignee.accountId != user.accountId So for all transitions you would need to add above condition, status would be visible only if a user is in group X and is not the assignee. Is it…

Hi @Berat Altunhan If I understand correctly, what you need is to hide all transitions except "Resolve" for assignee. Or is it more complicated? Are you in company-managed project?

Hi @Apoorva Srinivas K You are seeing the new workflow editor, there is an option to switch to the old editor Cheers

Not really, there is nothing you can do to prevent users from editing sprint in the issue view. But, for us, it was sufficient that Triage issues were not visible on Board ( you can change jql filter for that). That prevented mistakes, and was good enough.

Hi @Gavin McMenemy You could potentially make fields required during transitions. In my last project, we had two statuses before 'In Progress.' New issues had a 'Triage' status, and once all the information was collected, the PO would transition them to 'Open.' The backlog was configured not to show 'Triage' issues, so it…

Sure! Follow the steps: * Identify the Workflow:* Go to your Jira project's settings > 'Workflows'. * Find the workflow associated with the issue type where you want to enforce closing sub-tasks first * If you see the new editor, switch to the old editor. * Locate the Transition:* In diagram mode, click on the line…

Hi @Purvi Patel If you are in a company managed project, then there is ootb Subtask blocking condition, which will be much easier to use Cheers

Hi @Santhosh Kumar Arogyaswamy If you are on Cloud, then it is possible in any Jira expression-based validator including Script Runner. The expression you need is as follows: issue.customfield_10000.includes('state=OPEN') ? true : false where customfield_10000 is a Development field. You may need to adjust ID on your…

Hi @mekhak.bezhanian What do you mean by tasks opened by a reporter? Do you want to block some users from creating issues, or are you looking to prevent the reporter from reopening the issue?

Hi @Diana Osorio I think that described case can be addressed using a Jira expression-based validator. There are several options available on the Atlassian marketplace. I am from Forgappify, and we developed Jira Expression Validator, which is part of the Workflow Building Blocks for Jira app. The expression you need could…

Hi @Amzad Khan I am not sure about Automation, but it will be quite simple using any Jira expression-based validator/condition available on the Atlassian marketplace. I am from Forgappify, and we developed Jira Expression Validator/Condition, which is part of the Workflow Building Blocks for Jira app. The expression you…

Hi @Etai Leers For this case we've developed the Linked Issues Validator available as part of the Workflow Building Blocks for Jira app. Starting today, it can also be used to test the children of Initiatives or other higher-level issue types. Here’s an example of how it looks: I would appreciate it if you could give it a…

Hi @Sabyasachi Samal If your project is a company-managed project, you can use an app providing Jira expression-based validator. There are several options available on the Atlassian marketplace. We've developed the Jira Expression Validator as part of the free Workflow Building Blocks for Jira app. Feel free to give it a…

Hi @Marc Viladés It seems like you should be using a workflow validator. If the validator's condition fails, the user is prompted to fix the error before they can transition the issue. OOTB, in company-managed projects there is a Field Required Validator, which comes with some default validation message. In team-managed…

Hi @Mel Brooker You have several options, depending on what you want to achieve. 1. Assuming Root Cause is a custom field, make it required before closing the issue. To do this, add a Field Required Validator on all transitions leading to closed/resolved statuses. If you want to enforce it only for the "Bug" issue type,…

Comparing dates can be tricky, especially when working with teams from different time zones. Therefore we developed Dates Compare Validator, which is part of the Workflow Building Blocks for Jira free app. Below is an example of how it would be configured for: Due date that cannot be in the past. In order to enforce the…

Follow the steps: * Identify the Workflow:* Go to your Jira project's settings > 'Workflows'. * Find the workflow associated with the issue type where you want to enforce field to be mandatory. * If you see the new editor, switch to the old editor. * Locate the Create Transition:* In diagram mode, select the Create…

Hi @Chetan Krishna Sai Naidu/Jira-Admin If you're open to using apps or already have one providing Jira expression-based validators/conditions, then I think it would be a good option. For example, if you want only users with the 'Developers' project role to be able to create Story issues, add Jira Expression Validator to…

Hi @Harshal Rathee Did you successfully add the validator to the transitions? Cheers

If you're open to using apps or already have one providing Jira expression-based validators/conditions, then I think a simple expression would suffice: user.accountId != issue.reporter.accountId which would prevent the transition if the current user is the reporter There are several options available on the Atlassian…

Hi, The described case can be addressed using any Jira expression-based validator available on the Atlassian marketplace. I am from Forgappify, and we developed Jira Expression Validator, which is part of the Workflow Building Blocks for Jira free app. The expression you need is as follows: issue.resolution != null &&…

Hi @Matt Steadman I don't think there is a way in Jira out of the box. However, with any jira expression based validator you could validate if the attachments were added during the transition. You can search for apps providing jira expression validator on the Atlassian Marketplace I am from Forgappify, and we also…

Hi @thiago Out of the box in Jira, you can use the Regular Expression Check Validator against any Text Field. However, you would need to add the validator on every transition, including the Create Issue transition. Here's how you would configure it: If you're looking for a better validation message, you'll need an app with…

I've verified that the Team field is available in the Field Required Validator, which can be added to the Create issue transition. Could you confirm if you're using a company-managed or team-managed project?

Hi @Anush Chatikyan What would be the relationship between issue A and B in your case? I'm not sure if I understand correctly. Do you want to validate against a specific issue key? Beside the Linked Issues Validator, Workflow Building Blocks for Jira comes also with Jira Expression Validator, where you can build your…

Hi, If you are looking for a wizzard-like solution, we've developed the Linked Issues Validator available as part of the Workflow Building Blocks for Jira app. With a wizard-like UI, you can select options that represent your case. You can choose relations from: sub-tasks, parent issues, epic children, and linked issues.…

Hi @Victor Amadi Did you run "forge deploy" cmd before forge tunnel? Forge deploy is needed in case there were changes in manifest. Before that you also need to install the app on the instance by running "forge install" cmd. I would also recommend posting your question on the Atlassian Developer Community at…

Hi @Anush Chatikyan If you are open to using apps and looking for a ready-to-use solution. We've developed the Linked Issues Validator available as part of the Workflow Building Blocks for Jira free app. With a wizard-like UI, you can select options that represent your case and get it done very quickly. I would also…

Hi @Danilo Simic I don't think it's possible in Jira out of the box, at least not in an easy way. However, with a validator based on Jira expression, it would be simple, as follows: ["Catagory A"].includes(issue.project.projectCategory?.name) If the project is categorized as "Category A," then allow the transition;…

Hi @Peter Sarkar, I am from Forgappify, and we couldn't find an easy way to accomplish this in Jira Cloud using other apps, and it is not possible in Jira out of the box. Therefore, we have created the Linked Issues Validator as part of the free Workflow Building Blocks for Jira app. Please take a look at the configuration…