Maciej Dudziak _Forgappify_ Atlassian Partner

Thanks, now I have found https://jira.atlassian.com/browse/JRACLOUD-85094, which describes similar problem.

Hi @Marc -Devoteam- That’s very interesting—so there is indeed special handling for that field. Thank you for confirming it! I'm curious, do you know of any other fields that behave in a similar way?

Hi @Saad Ahmad If the out-of-the-box workarounds aren’t sufficient for your needs, you might consider using the UI Modification API available for Forge apps. This API allows you to customize certain parts of the Jira UI, including hiding or modifying fields and interface elements. You can choose to: Build a simple Forge…

Hi @thumuluru.shreya This is "by design". I have reported this problem to Atlassian Team, but it was rejected: https://ecosystem.atlassian.net/jira/software/c/projects/FRGE/issues/FRGE-1454. Recently I saw similar ticket open, but I can't find it at the moment. Unfortunately, there is no workaround at this moment. If a…

Hi @sumit pandey I’m from Forgappify and we developed the Ultimate Validator, which is part of the Workflow Building Blocks for Jira app. It lets you use most of the power of Jira Expressions—but without writing code. Instead, you build conditions through a simple UI Here’s how the configuration for your case would look:…

Hi @Vikrant Yadav There is a closed list of fields that work with UI Modification API: https://developer.atlassian.com/platform/forge/apis-reference/jira-api-bridge/uiModifications/#issue-view--preview- Comments and Linked issues is not supported yet. A Jira expression-based validator would be the way to go. There are…

Hi @tony.gonzalez 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 app. Because the second field in your case is a paragraph, the…

@Jack Brickey I got the same error, when I forgot to remove the field from the Choose fields dropdown

Hi @Jack Brickey This is something that works for Single Select { "fields": { "customfield_10044": { "value" : "{{issue.parent.customfield_10044.value}}" } } } :) Cheers

Maybe, I am not familiar with the server version, however on the Cloud it is not possible

The Condition executes the code, if that code returns false, then the condition hides the transition ;)

Hi @thumuluru.shreya 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 its wizard-style UI, you can easily configure which link types to validate and enforce that at least one such link must…

Oh in that case, I am afraid it is not possible in Jira yet. Here is a full list of supported screens and projects: https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-ui-modifications/#global-issue-create It is a limitation for all the apps leveraging this API including Behaviours I know that…

Hi @Ana Luiza Chagas If you are open to use apps, you may want to look at the app my team developed - Field Rules – UI Modifications for Jira. It includes a Make field required rule, which allows you to make a field required dynamically based on selection in other fields. It is configured via UI, no coding needed. The rule…

Hi @mark laney I believe you might be using the new Workflow Editor. As far as I know, it currently doesn't provide a straightforward way to add screens to transitions. You may want to switch back to the old editor, where this option is available, and follow the instructions you’ve found. Cheers

Hi @kedar If you are open to use apps, you may want to look at the app my team developed - Field Rules – UI Modifications for Jira. It includes a Hide field options rule, which allows you to hide specific options of supported custom fields. The rule comes with extensive precondition settings, including user groups, project…

Hi @Sanam Malleswari I’m from Forgappify, and we’ve developed a collection of validators as part of the Workflow Building Blocks for Jira app. One of the latest additions is the Ultimate Validator, which looks like this: With its simple UI, you can easily configure conditions such as: Allowing a transition if "Yes" is…

Hi @Sanam Malleswari If you are looking for a conditional validator, there are couple of options on the marketplace, just look for jira expression validator. Cheers

Hi @Amal Johnson If you're open to using apps, our team developed Field Rules – UI Modifications for Jira. It includes a Hide Issue Types rule, which allows you to hide specific issue types on the Global Issue Create view. The rule comes with extensive precondition settings, including user groups, project roles, and even…

Hi @Marc -Devoteam- Yes, it would require 3rd party app

It would be possible with Jira expression-based validator, e.g.: issue.parent != null && issue.parent.issueType.id == 10006 && ![10011].includes(issue.parent.status.id) Basically, you could create a Validator on Create transition, which would prevent child issues to be created when a parent is of issue type = Feature and…

Hi @Anshuman Ankur Do I understand correctly, that you have a custom hierarchy: Epic -> Feature -> Story / Tasks Therefore those applies: 1. a parent of the Feature is Epic, 2. a parent of Story/Task is a Feature 3. There can be several Features under 1 Epic, and you want to block creation of subsequent Features until…

Hmm, I don't believe it's possible. As far as I know, the Asset field type is not yet supported by the UI Modification API on Jira Cloud. Or am I mistaken?

Hi @Samarth Sharma It should be possible with Jira expression-based validators provided by third-party apps; there are a couple of options available on the Atlassian Marketplace.It comes down to validating the content of the Development field, which might seem tricky at first glance, but it is not that hard. The value of…

The app comes with both: * Linked Issues Condition * Linked Issues Validator Condition hides the transition, validator prevents the transition (also create) and prompts user why the issue cannot be transitioned

Hi @Sreenivasaraju P With Jira Expressions, it is possible to load an issue by its key. So, if there are no other relationships involved, this can be used within a workflow validator. Could you share a bit more about your use case and whether a validator would be sufficient? Cheers

Hi @Jyoti Patel For this exact case our team 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. Additionally,…

Hi @Lance Waldrop It is possible with Jira expression-based validator to check whether time is logged before or during the transition, but that requires 3rd party app. Sorry for the link, but I am on a train, I have answered similar question here:…

Hi @Sachin Guttala I 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 Workflow Building Blocks for Jira app. With simple UI you can decide which links should be checked and in…

You're welcome