We have an issue where we only allow time tracking to occur on sub-tasks. However, via the backlog issue view, a user can edit the Remaining Estimate on a story. Due to our various conditions in our workflow, this creates a problem for us since we only want to use sub-tasks to for time tracking. I've tried the behaviors plugin to make the field read-only but it doesn't stop the ability to inline edit. Any ideas would be appreciated!
Our current solution is a series of conditions for our Story workflow that will require the Remaining Estimate = Null in order to proceed but if we can stop it at the source, that's what we would prefer.
2016-03-28 14_44_33-OSSENG - JIRA Development - Agile Board - Windstream JIRA.png
i have questions pertaining to this.
1. I can take the time tracking out of the edit screen to prevent users from changing the original estimates, however, if i want the managers to be able to edit the time tracking/original estimates, what screen would i put that in, or how would i restrict those fields to users with certain permissions?
2. The Remaining Estimate field is in the Log Work section, so my employees can edit that field. I need the employees to be able to log there time for the JIRA issues, however I don't want them to be able to edit the Remaining Estimates field. How can i make that field on that page read only?
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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