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; } } }

Time tracking validator not working

Johnathan Garrett-Sinclair

I have used the "Time Spent" field for Field Required validator and the "Log Work" field for the Screen to ensure engineers input the time they spend on tasks when transitioning tasks.

However, I cannot progress past the screen when testing as it thinks I have not input a value into the Time Spent field (even when I have - see the pic below)

Time Spent Issue.PNG

Accepted answers

All comments

Zoryana Bohutska _SaaSJet_

Hi @Johnathan Garrett-Sinclair

You can check this documentation https://confluence.atlassian.com/adminjiracloud/configuring-time-tracking-818578858.html

Regards

Johnathan Garrett-Sinclair

Thanks but this only tells me how to set up Time Tracking, not how to add it as a validator and fix the issue I am having once it is being tested

Jack Brickey

So you might have a look at this thread - Time-Spent-required-on-Transition

However, I spent 15m on this and I concur that it does not seem to work. That is, if you use the Field Validator for Time spent and prior to the transition you have logged work the transition will fail which would seem to say the utility still sees the field as empty. Now, I may certainly be overlooking something here. I have opened a question with Beecom the developer of jsu-automation-suite-for-jira-workflows to see if they can share some color on this. Assuming I hear back I will comment here.

BTW, while opening the ticket, I noted some release notes that initially looked promising. Seeming to convey a bug was fixed at one point. I have to wonder if the constant change to Jira Cloud hasn't possibly unraveled things. I want to say that this has worked for me in the past but simply do not recall definitively and I do not use it currently in any of my active projects.

Jack Brickey

and this just in from Beecom...

Condition/Validator: Atlassian decided in 2016 to go 'Cloud Native' with their Jira Cloud. They called it the 'big fork' as the started to fork out for Jira Server.

Atlassian integrated all Condition & Validators from JSU and you can find for all JSU Condition & Validator a native Jira Cloud Condition/Valdiator.

On Jira Cloud, Field Required Validator is maintained by Atlassian, I would suggest to please contact Atlassian for better support. For JSU on Jira cloud documentation, you may have look on https://confluence-apps.beecom.ch/display/JSUCLOUD/JSU+Configuration+Guide

I had forgotten this. :-) ...

So I will open a request w/ AS.

Jack Brickey

@Johnathan Garrett-Sinclair, I wanted to circle back an close off on this. I opened a ticket w/ Atlassian and had a discussion w/ them. Basically, this is working as designed but the Help text and documentation is leading you to believe it works differently, i.e. the way you & I had hoped. Hopefully this brings some closure to your question.

here are the details....

I definitely understand that sometimes the text implemented might not be the best and I also checked that our documentation about this does not explain the difference between each validator:

Advanced workflow configuration - Validators

I ensure you that I'll take this forward and raise awareness about this documentation misunderstanding.

Field Required Validator --> Field must not be empty during the transition.
Field has been modified Validator --> Field value must be changed during the transition.

The major difference between these two validators is that the Required Validator only validates if there is a value on the field, while the other one validates if this field's value is being changed, for example, if you set a version number and the field asks you to change it after some transition, it will not allow you to keep the same existing.

Johnathan Garrett-Sinclair

@Jack Brickey Thank you so much for all this information, I must admit I am a bit overwhelmed and haven't fully digested it but in short does this mean a compulsory Time Spent Field is not possible?

Clifton Foster

I got around this by adding a transition screen (NC: Task Done Screen) with Log Work in it. I then added a Validator "Field Log Work should be modified during the transition." I did not check for previous Time Spent value but just required a new time entry. Here are the screenshots from my implementation. All that needs to be done in the transition screen is to fill out the Time Spent field (and the Assignee and Departments in my case).

Transition Screen - NC: Task Done Screen

Transition Validations

Transition Screen Fields

2022-03-30 16_35_07-Configure Screen - Jira.png

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

time-tracking

validator