how can we restrict Original Estimate modification for a specific role

[Sivarama Krishna K]

HI,

In Time Tracking, I would like to allow update.

But when I include in EDIT Screen, every one can edit Original Time Estimate.

But, I would like to give this option only to specific role.

Let me know what is the possibilities.

[Sivarama Krishna K · Accepted solution]

For the selected workflow, I am able to use Self Transition method (Source state and Destination State both are same) and able to achieve the requirement fulfilling.

But this action to be done for each and every workflow.

Anyhow, I am able to get it done.

[Niranjan · Accepted solution]

Hi @Sivarama Krishna K ,

A simple option would be to remove the field from Create and Edit screen. Add it to view screen.

Create a transition with a transition screen. You can add the field to the transition screen and restrict the transition to specific roles using workflow conditions. You can make the field required during the transition. Ensure that you have outgoing transitions to all statuses.

[Sivarama Krishna K]

Thank you.

This way I can make it.
But the status shoudl not be changed. If we make a transition, the status will be changed to new status.

I want to do it like "Assign" button kind of action.

No change in Status. Only Value to be updated.

[sanooj kumar]

A work around would be to add a custom field and populate it with the original estimate when it is entered for the first time. The custom field can be a non editable field which can be populated thru automation. This will help you capture if the estimation was modified or not and still have the original estimate recorded.  

[Maxim Gromov]

1. There is no way in Automation to trigger on Original Estimate (only Time Tracking, which will trigger even when team logs their hours).

2. There is no way to make field editable only for Automation

I was thinking JIRA is good software until i started to manage it myself. And that's so annoying, how many things are over complicated. As a result whole team spends lots of time on discussions around Development process, trying to fit it into JIRA software realities, instead of doing real work and performing on the project...