Our organization wants to be able to track travel requests through Jira and I know there are many templates that can be used for tracking requests so I have that covered.
Our organization has 6 different teams with approvers for those travel requests.
At the start of each year each of those teams is allocated a travel budget and then they need to track the estimated costs and actuals for each of those requests to ensure that they do not go over their total budget. We want everybody in our organization to be able to submit travel requests, and have them queued to the appropriate team for for approval and overall tracking of estimates and actuals against their budget.
We would like to keep the form and issue type generic since the information collected is the same regardless of team. I created custom number fields for estimates and actual costs and a custom field for Team (single select that includes all the teams in our organization).
I considered using Parent Epics to capture each teams budget for the fiscal year and those epics would be created each year by our budget team and those epics would track both the total estimated costs and the total actual costs so that the leaders for each of those teams could see where they were by looking at the epic.
I was successfully able to use Automation by following this thread -
https://community.atlassian.com/t5/Jira-Work-Management-Questions/Jira-Automation-for-budget-cost-sum-per-epic/qaq-p/2620541 and changing the Epic link part to Parent so I know I can get the summing of all the approved submissions.
However, I was hoping to set up automation when issues were created that allowed the submitter to choose the appropriate parent epic - I saw that was not available although I did vote for it -
https://jira.atlassian.com/browse/JWMCLOUD-527
I then figured I could set up automation to automatically link to the appropriate team fiscal year epic but it looks like my only option is Trigger Issue or Most recently created issue despite the note in the UI saying You can link to the issue that triggered this rule, previously created issue, a smart-value or simply an issue key.
So now I am stuck and not sure how to proceed. Does anybody out there have a similar use case that has been able to successfully implement in Jira, Jira Software, JWM, or Jira Service Management? If so, can you please share the details. Unfortunately our budget does not support purchasing an add on to handle it for us.
