Substract work logged from individual tickets from number of hours defined for a project.

[Nawaaz SOHAWON]

Hi,

Any ideas/suggestions for the below scenario to be implemented in JIRA:

1. Project A has a set number of hours defined for support. Ex: The project has 100h of support to provide to the client. 1st question: Can we create/set a field which is specific for one project?
2. Once a ticket is resolved and the total time logged is acquired for resolution, this "total time logged" for the ticket should be substracted from the "number of hours" defined for the project. Ex: The ticket took 2h to resolve. Hence those 2h should be substracted from the 100h; which leaves only 98h of support remaining. A second ticket took 3h to be resolved; which means the hours remaining for support should now be 95h. 2nd question: Can this be automated?

Thanks for any possible leads/suggestions.

Regards,

Nawaaz

[Jimi Wikman]

1. Yes you can. In the field you can define context and values. This way every project can have different values in one custom field.
2. Yes and no. depending on your setup and if you use Advanced Roadmaps or not this can be done in different ways. The "easiest solution" if you just use JSM and Jira Software is to add a separate Jira Software Project where you create an issue of your choice for each project. In that issue you set an Estimate and as you resolve tickets you log time in that ticket to get remaining time as well as a log of what work you have done.
   
   If you use Advanced Roadmaps then you can extend the levels above Epic with Project levels and do the same thing in that project issue. The difference is that in the Advanced Portfolio Plan you will have automatic rollup of activities connected below it.

[Nawaaz SOHAWON]

First I would like to thank you for your prompt response @Jimi Wikman 

1. Yes you can. In the field you can define context and values. This way every project can have different values in one custom field. --> The thing here is that this field will then be available of all tickets. However I would like to create a field which is more of a project property. That way, i can say that i have 110h for Project A and 200h for Project B,etc.
2. Yes and no. depending on your setup and if you use Advanced Roadmaps or not this can be done in different ways. The "easiest solution" if you just use JSM and Jira Software is to add a separate Jira Software Project where you create an issue of your choice for each project. In that issue you set an Estimate and as you resolve tickets you log time in that ticket to get remaining time as well as a log of what work you have done. --> A very clever and ingenious way indeed. I will give this a shot. But I am only using JSM and not Software. I am thinking of creating a Request Type called Technical Details and log the total hours for the project as a specific field for this Request Type. Then I would substract the work logged from a ticket (when it is resolved) from that total hours value. In your proposal, i would like to automatically substract the time logged from a ticket from the total hours. The issue here is can we log this time spent as numbers only?

Thanks a lot,

Nawaaz

[Jimi Wikman]

You can also create a custom issue type called project and then link tickets to that. As this will be a blank issue you can use the description to log times in a list format to keep track?

I don't think I have ever just used JSM, but you have estimate and time logging for issue types there are well, right? Then you can activate it only for the project issue type?

[Nawaaz SOHAWON]

Thanks again Jimi.

Yes the estimate and time logging are both activated. 

I have created the custom issue type "Project Details" where I have input the "total hours" for the project. But I have created it as a Sub Task and linked it to the ticket being worked on. The "time spent" to resolve the parent issue is indeed translated to the sub task ("Project Details). However I am not able to link this Sub Task to all my tickets.

I am wondering now if I have to create "Project Details" as the parent ticket and the other tickets (incidents, support,etc) as Sub Tasks.