This could be poor workflow design on our part but here is what we are experienceing.
We have made TIME SPENT required on the transition (validator) to CLOSED status. The problem is when user moves an item WHICH ALREADY HAS time spent to CLOSED status, we get an error saying TIME SPENT is required and are prevented from changing status to CLOSED unless we add more time on the Resolution screen.
If anyone has suggestions on how to correct this, I would love to hear them.
Ultimiately we just want to make sure that by the time an issue in Closed status, there is some time on it.
we are on jira v7.2.1 and have tempo timesheets
...PermissionsStartOnly=true User=www-data Group=www-data ExecStart=/opt/jira/bin/startup.sh ExecStop=/opt/jira/bin/shutdown.sh TimeoutStartSec=120 TimeoutStopSec=600 PrivateTmp=true [Install] WantedBy...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs