TLDR: Can Jira Automation Rules create project components?
End Goal: (Relative to an Automation Rule)
- When rule triggered,
- Create new project component named: { "Onboarding of" cf[10901] }
- Apply that component to trigger issue (so its children can just inherit it)
cf[10901] aka "Name" is the custom field for the new starters name.
Context/Background:
I've been making a set of rules, that automate the process of creating the mannyy tasks involved in onboarding a new employee.
I realise now that some 30 tasks are made for each new starter, and I was considering how to categorise each individual new starter - Imagine putting them into their own little folders, and inside are all of the issues related to them (or related to that component).
I have completed the actual rules for making the tasks to onboard them start to fin. The first of which is a 'starting point' rule. That rule creates the backbone of the many rules after it. The starter essentially creates the core tasks, which the many others then are parented by...
That starting rule is triggered by the creation of an issue of the type "New Starter", along with some error handling.
There is a custom field cf[10901], which contains the new starters name. This already inherited by every task.
Postscript:
I did try simply using the additional fields to add a non-existent component, unsurprisingly it did not work.
I am exploring different outcomes, not in line with my goal, as I am not sure my goal IS actually obtainable.
If you think that the above is not possible, are there any other methods you may recommend?
I'm not using sprints, epics or versions - might they help?
Jira Version: Datacentre - Atlassian Jira Project Management Software (v9.12.11
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.