I want to set up conditions in my workflow to force engineers to "Original Estimate" before pulling an issue into "In Progress" and "Log Work" before pulling it into the final status of "Accepted"
I have successfully created an easy rule that forces them to add an "Original Estimate" before pulling an issue into "In Progress" using this simple condition:
Where I am having issues is forcing someone to "Log Work" before pulling issues into "Accepted". I am using the same condition so I dont understand what my issue is, please see issue below.
Here is a screenshot of a test issue that I logged work but I am still unable to pull the issue into "Accepted"Any help would be appreciated.
Thanks for reaching out to Community!
@Célestin Mansouri-Deveaux, I saw that you created a ticket with our support, and the issue was resolved as well.
I know it has been a while, but I would like to share some details here in case other community members face the same issue.
The resolution for Brett’s case was to add a Screen during the transition, to make sure it would only transition to another status if the “Log Work” was not empty.
When adding a Validator to a workflow, it’s necessary to add a Screen with the field you need to be filled, otherwise, the Validator will not work as expected.
For more details, please check the documentation below:
By using a transition Validator + custom screen, that screen is always shown, even if the issue already has some worklogs, and in the transition screen a work log must be inserted (even though 0 time can be used...).
This is a lot less than ideal !
If I only need a check of type "some time has been logged on the issue before transition is permitted", this is not currently possible. A transition condition of type "Value field" cannot be done against Time spent, and checking against "Log Work" (!= null type String) does not function.
Why isn't sum (Time spent) available as a field against which a condition can be built?
I've seen i referenced on this question, but for the love of God I cannot find it anywhere on a Software Development (Classic) type project in Jira Cloud...
I've tried logging time 3 seperate ways with no success, by using the "work log" option by the comments, i've filled in "time spent" and i've used "log work" in the drop down on a ticket that gives more options. All of these added to the "Time Tracking" field but none have allows me to pull the ticket into "accepted"
That's very strange. However, one thing I notice is that you have > null. Maybe try putting in 0 for the value and not null. So > 0
If you do a filter for Key = LOD-67 and add the columns for Log Work, Time Spent, and Time Tracking. Do you see values in those?
And whichever one(s) you see a value for, I would try that field with the > 0
@John Funk any feedback on that elevated ticket ?
I too cannot build a transition condition of type Value field on Time spent.
Building it against Log work does not work, no matter the condition configuration...
@Angélica Luz 's solution using a transition Validator + screen has a series of issues that renders it a non-usable...
Hi All! We’re excited to share the launch of an announcement banner that lets Jira site administrators communicate directly to their users across their Jira Cloud instance. ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events