Maciej Dudziak _Forgappify_ Atlassian Partner

Hi @Sandy Huanco The Field Required Validator, available out-of-the-box in Jira, ensures that fields are not empty during a transition, including Create issue transition. However, it only works when a transition screen is present. For example, if you added an attachment on the issue view and then tried to change the…

Thank you for your kind words, I'm so glad to hear that!

Hi @Inna S There is no out-of-the-box solution. You need to look for a workflow validator that is based on custom jira expressions. I don't know JWME, but I am guessing that they have some kind of custom/script validator. If you want to learn how to build custom expressions, our team built Linked Issues Validator, also for…

Hi Harshad, Do you have the Work Log field on the transition screen? If yes, I’ve answered a similar question here: https://community.atlassian.com/t5/Jira-questions/Re-Ensure-Time-has-been-logged-on-Transition-to-Closed/qaq-p/2838858/comment-id/1059171#M1059171 Cheers

That’s great! I’m happy to help. :)

Hi @Jannis Thank you for your interest in the app and your question. Please correct me if I’ve understood your requirement correctly: if you want to simply ensure that time is logged either on the issue itself or on any of its subtasks, the following might suffice for you: issue.timeSpent != null ||…

Hi @mohanbabu.s It’s great to hear that the app met your requirements :) Cheers

Hi @Enrique If you want to learn Jira expressions through examples, I can suggest trying the app our team developed —Workflow Building Blocks for Jira. It includes wizard-like validators, such as the Linked Issues Validator. With just a few clicks, you can create a validator based on a Jira expression. What might interest…

Hi @mohanbabu.s It is not possible out of the box. However, with apps, there is a UI Modifications API that can limit the visibility of options. This works with some limitations for Jira Software and Jira Work Management projects. Based on mentioned API our team has developed the Field Rules - UI Modifications for…

Hi @[deleted] Actually, I don't think so. A board is conceptually not tied to any specific workflow. What is displayed on the board depends on the JQL. By editing the JQL, you can even include issues from other projects. You can display issues from multiple workflows on a single board, or if you restrict the JQL filter,…

I am guessing that on your Jira instance, "Customer Request Type" is the field you are looking for. Some time ago it was how it was named. There are 2 ways to confirm it: 1. Check your field configuration and look for it, most probably it will be a Locked field with some description pointing to the correct one. 2. Use…

Hi @Jerome F_ Yes, the Request Type field is definitely available in Field Required Validator, and it works. I did tests. Are you using the old editor?

Hi @Jerome F_ I have checked and confirmed that the workflow Field Required Validator available in Jira is working. Start typing in the field and search for the 'Request Type' field to ensure that users select a request type other than the 'No Request Type' option. If more complex validation is needed, it is also possible…

Hi @Jerome F_ A lot changed since 2021. I believe it is possible to make it required using workflow validator. Is it a company-managed project. Do you want to make it required on Global Issue Create?

Hi @Alexandria (Lexi) Codd If you're interested in alternatives to validators and are open to using an app, our team has developed Field Rules - UI Modifications for Jira. In one place, you can create a UI Modification—a list of rules applied to a selected context, defined by a project, issue types, and view type (1000…

Hi @marianna_taborda Unfortunately, Jira workflow editor for team-managed projects don't yet support third-party validators; I am afraid, right now, only use in company-managed projects is possible.

Hi @Pierre Guyénot It is not possible out-of-the-box, but 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 app. With a wizard-like UI, you can select options that represent your case. You can choose…

It is written in Forge, maybe company will allow it. I don't think it there is another solution, and slowing down the transition is definitely not possible.

Hi @Sebastian Krzewiński Team field is visible in Jira expressions except for Create issue transition. I remember testing it. There is also an open bug for the Create transition: https://ecosystem.atlassian.net/browse/ACJIRA-2504 Cheers

Hi @marianna_taborda I think the best approach would be to use a Jira Expression-based Workflow Validator, which will consistently prevent the transition when conditions are not met. There are several options available on the Atlassian marketplace. Our team at Forgappify has developed a specific validator for linked…

Hi @Brian Taylor 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 app. With a wizard-like UI, you can select options that represent your case. You can choose relations from: sub-tasks, parent issues,…

Hi @Chandrashekhar Kavi In Team-managed projects, workflow validator/condition options are very limited. Unfortunately, it may not be possible to achieve this directly. If you can migrate the project to a company-managed project, there are some third-party apps that can help you accomplish this. Alternatively, you can try…

Hi @최보훈_품질경영실_KBN It depends on your use case. If you are using a Parent <-> Sub-tasks relationship, there is a built-in Sub-Task Blocking Condition in company-managed projects. However, if you're working with higher levels in the issue hierarchy, such as Epic <-> Story, there is no out-of-the-box solution for this in…

Great to hear that! I’m glad I could help :) Cheers

That will ensure that time is logged before the transition can be completed. On the other hand, if you want to ensure that time is logged during the transition (if you have a dedicated screen and added the Log Work field), you can check against originalIssue—which is a snapshot of the issue before the transition screen was…

Hi @Oliver Skelton If you want to check if at least 1 hour has been logged in the issue, then use the following Jira expression: issue.timeSpent != null && issue.timeSpent >= 60*60 There are several apps providing Jira expression-based validator available on the Atlassian marketplace. I am from Forgappify, and we developed…

Hi @Ramya Srinivas 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 app. With a wizard-like UI, you can select options that represent your case. You can choose relations from: sub-tasks, parent…

Has anyone used Workflow Building Blocks? I’m curious if you’ve found our Preview panel for validators useful, which aims to help you learn Jira expressions and later build your own custom, more complex validators and conditions.

Welcome @Tyler Rathbone I’m afraid that’s not possible in Jira out-of-the-box. However, if you have an app or are open to using one that offers Jira expression-based workflow validators/conditions, it may be achievable. The key question is how you would differentiate sub-tasks that block other sub-tasks. Do they share…

Hi @Aravindh P It is not possible to prevent a transition using Automation; you can only revert it (i.e., transition the issue back to its previous status). If you want to prevent the transition, you need to focus on workflow conditions or validators. While there is no out-of-the-box validator, there are apps on the…