Best practice: How to store issue related values (e.g. number of transitions)

Currently we're using script runner to update some custom fields (configured as text (read only)) to track the number of transitions. But unfortunately we don't want to distract the users on the screen with these values. It's more an internal thing which should be accessible only to a few people.

 

Currently I don't see any other approach than having these custom fields on the screens. Otherwise we are unable to edit the fields during transitions.

 

I guess we are not the first ones running into to issue so my question is: is there a better way to store issue related values internally? 

 

 

1 answer

0 vote

Are you Cloud or Server?

I ask because Server scripts should let you set fields that are not on screen (and do scripted fields which also don't have to appear on screen, and could do the calculation based on the history instead of updates)

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published 4 hours ago in Jira

5 ways you can make the most of Jira Software and Bitbucket Cloud

As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...

16 views 0 3
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you