I used an automation described here: https://community.atlassian.com/t5/Automation-questions/Sum-up-Story-points-to-epic/qaq-p/1389224 to automatically sum up the Story Points on my Stories and update the linked Epic.
I would now like to make the "Story Points" field on the Epic read-only so that nobody accidentially overwrite the automated summing up from the Stories.
I did a little research and saw that this could be achieved with ScriptRunner Behaviours, but that is only available for the Server version, not the Cloud. So I am wondering whether there's a different alternative for the Cloud version or any other possibility how I can make the "Story Points" field on Epics read-only?
Hi @Sabine Do-Thuong - If your Story points of Stories sum up to Epic, then remove the Story points field from your Epic's edit and create screen which will make them read only. You need to have it on view screen though. You do not have script runner behaviors in JIRA Cloud.
@Niranjan thanks for your hint. I just tried it. It works well for the old issue view. The problem is that with the new issue view there is only one screen to view and edit, see also: https://support.atlassian.com/jira-core-cloud/docs/what-is-the-new-jira-issue-view/
Because of this missing separation of screen your suggestion unfortunately doesn't work.
@Sabine Do-ThuongJust tested. The suggestion from Niranjan works well as of today in Jira Cloud.
I did the following:
- created a new screen (a copy of an existing) where the field which should not be to edited by the users is removed
- assigned the new (copied) screen to the project's corresponding Screen Scheme (assigned the issue action of edit to the new screen)
It works as intended.
For the link you cited, yes, there is a change that happened on Jira Cloud - I just can interpret it in a way that screens are "initially" the same, but you can adjust and make your requirement happen - just give it a test, it works.
@Daniel Ebers thanks for your input. I just tried it out and it still doesn't work for me. Here are two screenshots that maybe illustrate better what I mean:
Old issue view:
New issue view:
So the behaviour works as expected on the old issue view, but it does not work on the new issue view?
That's weird, in my tests it was displayed but I could not change the value for the field. So you are saying that you can edit "Story Points" in New Issue View although you have a separate screen for "Edit" which is indeed not enlisting the field in your configuration?
If this is a "yes" then our instances differ in behaviour.
Yes @Daniel Ebers, that is exactly what I was trying to explain. I have 2 different screens, one for "View" and one for "Create" and "Edit" - the Story Point is only configured for the "View" screen, but not for the other. It works properly with the old issue view. But on the new issue view I can nevertheless edit the "Story Points" field.
I took a quick look through Atlassian's public bug tracker, and it looks like this has been reported here: https://jira.atlassian.com/browse/JRACLOUD-75712
I'd recommend voting on this issue and adding any details that are specific to your use case on that bug.
Sorry I can't offer any more help!
Hi Atlassian's, How is your journey with #Atlympics 2021 so far....excited! Me too, same excitement. Here's my typical team planning and vision dashboard which I used to share to my management and ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events