@Yamuna Ramasubramaniyan, You could change the field name but that would be global and I am not entirely sure of the ramifications. A better way might be to update the fields description, either on the global field object or the field configuration scheme letting the user know this is an estimate.
You could also get really creative and create a new field called estimate and then use one of the workflow add-ons to copy the value to the story point field upon create or transition.
Thanks Peter. Yes, am wary of changing the name of the field as well. I was hoping to use the same Estimate field label that Jira shows in the backlog view everywhere. The new field idea is also interesting, but not sure the roi compares to just telling my users to get used to seeing story points and estimates as the same thing :)
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
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