Hi,
I have two projects, Incident Management and Problem Management. In the Incident Management project I have a field titled 'Total Agent Hours' that we fill in with a numeric value at the end of every incident to reflect how many hours it has cost us from an end user CS agent perspective. We then link our incidents to problem tickets in the Problem Management project. One problem can have multiple incidents linked to it if necessary.
I would like to be able to set up a rule or automation that takes the 'Total Agent Hours' value from the incident tickets and returns a sum of them on the problem ticket. I would like this to update each time a new incident ticket is linked to the problem ticket so as to show a running total. For example:
Incident ticket 123 has a value of 10 agent hours, when it is linked to problem ticket 123 the value of 10 is shown in the agent hours field.
Incident ticket 345 has a value of 20 agent hours and is subsequently linked to problem ticket 123. The value in he agent hours field should now read 30.
Is it possible to set this up using Project Automation? We do have scriptrunner installed, but this seems more complex to set up and I am the only one that can set these things up and I'm not good with scriptrunner!
Many thanks for your help.
You need to also add those issue types for that field and for your project. Within the administrative area, go to Custom Fields and locate Story Points. From the action column, select Configure. Then Edit Configuration and select the Bug and Improvement types. If is not associated with all projects, then you want to ensure your project is selected. Then, you'll want to make sure they appear on the Jira screens that are associated with that field as well.
Thank you Karie,
The best and most straightforward answer I've found about the subject!
Ramon Maria Gallart
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Great answer. Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
3 years and this answer still applies and saved me many hours of why the field would show up for stories and not for bugs, even when they were using the same screen.
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am perhaps have the opposite problem - for my project we don't want to have the story points field available for Bugs.
I can't follow the above solution because if I disable it then it will affect ALL the projects - no bugs would have story points (which is right in my opinion but some of our teams don't want to work that way).
I'm looking at the Screen Scheme that Bugs use and can't see Story points...so I'm a bit perplexed. Any ideas?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Karie. That's still saving time in having to figure it out, five years later. ![]()
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Great answer! Saved my day! Just needed 2min to implement :-)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi there, I'm having a similar issue.
I have already configured the story points custom field contexts' (all tickets, all projects).
I have ensured that story points custom field are associated to the screens for the project, and that they are visible.
The estimates tab in the board settings is still disabled...
Am I missing a step?
the goal here, for simplicity, is to have the every ticket have the field.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks, Karie. Your instruction is still good
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the detailed answer. It still corrects and is useful to me in 2018.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.