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 votes

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 Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,755 views 11 18
Join discussion

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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot