nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Original estimate field mandatory when making a transition from TO DO to IN PROGRESS

Laviniu Chis

Hello
I work with a team management project in Jira - Kanban flow. But I have the same issue in company management projects as well.

I want to make Original Estimate field as mandatory (a) when creating a new issue or (b) when transitioning an issue from a TO DO to IN PROGRESS status. I can add the field in the issue layout.

My problems are the following:
1. When I tried to make Original Estimate field mandatory, I didn't find it anywhere. Is is missing from the "Issue -Configuration Fields".
2. When I tried to create a rule for my workflow (start work transition) this field is missing again from the drop down list, but instead I see other custom created fields.

Any ideas?

Accepted answers

All comments

Kuan Yi Ming (ServiceRocket)

Hi @Laviniu Chis

I believe this may be a limitation of Jira Cloud, as I do not see any viable automation or transition rules for a team-based project's issues that meet your requirements.

Until Atlassian implements the ability to add the Original Estimate field as a required field in a team-based project, one workaround would be to use an Atlassian Marketplace app that enables custom post-functions that can be triggered by Jira events such as Jira Misc Workflow Extensions or ScriptRunner. These apps can then check if the issue has no Original Estimate field set, and then run an appropriate workflow transition to revert the issue to its previous status automatically while displaying an appropriate error message to the user.

Regards
Yi Ming

Rohan

Hi Laviniu,

For Original estimate this is not possible in Jira natively; however, we are tracking this in the feature request below. I would suggest you start watching this feature request to receive future updates.

Conditionally or dynamically mandatory / required custom field based on the value of another field

The only similar scenario would be achieved following the idea of "workflow transitions", but this is not exactly your request.

While transitioning an issue from one status to another, if a particular field value is selected, we need to enforce the mandatory status of another field.

Maciej Dudziak _Forgappify_

Hi @Laviniu Chis

In company-managed projects it is possible using expresion-based validators provided by apps, or if you need only a condition, there is ootb condition you can use. Note that you need to switch to the old editor, cause, in new editor you won't find the relevant options. I answered similar question here: https://community.atlassian.com/t5/Jira-questions/Re-Workflow-Condition-How-to-set-condition-for-field-Or/qaq-p/2655223/comment-id/935856#M935856

Cheers

Laviniu Chis

thank you for your answer. Unfortunately for the team managed software project template I can not switch between old and new editor. I'm stuck with the new editor.

Laviniu Chis

Thank you @Kuan Yi Ming (ServiceRocket) for your solution. I tried ScriptRunner but it is to technical for me. I guess I'll wait for the possible development of this feature as @Rohan suggested.

Laviniu Chis

Thank you @Rohan for your answer. I'll wait for the possible development of this feature.

Derek Preston

The following regex in a "Validate a field" rule worked well for me.

^(?!\s*0+\s*[a-zA-Z]*\s*$).+

Derek Preston

This was used in a company-managed project workflow.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud