force or overwrite a selected issue type when creating a linked issue and assign the issue type of t

[Angel Salazar]

Hi guys, I have a question for you. Is it possible, or is there a way, either through a postfunction or Scriptrunner script, to force or overwrite a selected issue type when creating a linked issue and assign the issue type of the parent issue?

 Example: I create an issue with an issue type “Incident” and then from that parent issue I decide to create a linked issue and select the issue type “Monitoring” on the creation screen. What we want is for the linked issue to be created with the issue type ‘Incident’ rather than “Monitoring,” which is the issue type of the parent issue.

In summary, what the customer is asking for is that regardless of the issue type selected when creating a linked issue, when it is created, it takes the issue type of the parent issue.

[Angel Salazar]

Hi @Trudy Claspill 

Yes, what they want is to change the issue type after the linked isuue has been created.

I don't really see much point in this, but from the client's point of view, they want to prevent people on their team from making mistakes when selecting the wrong issue type when creating a linked issue from its parent issue.

That's why they want this kind of override or forcing that makes it so that regardless of the issue type chosen when creating the linked issue, once created, this field is overwritten and takes the value of the parent issue issue type.

Yes, they use the same workflows, screens, fields, conditions, etc.

[Trudy Claspill]

Hello @Angel Salazar 

Can you clarify this point?

Are you looking to have the selected issue type forcibly changed before the issue is created, so it uses the screens/workflow of the desired type?

Or are you looking to have the issue type changed after the issue has been created?

If the latter, do your various work types all use the same workflows, screens, fields, etc. including validators, conditions, which fields are required, etc.?

While it may be possible to force the change of the work type after it has been created, there can be problems or unanticipated consequences when the source type and destination type don't use the same configuration. What if the destination type normally requires a field that is not required by the source? What if the person who created the source work type item is not normally allowed to create the destination work type?

[Trudy Claspill]

Given that you say they are using the same workflows, screens, fields, conditions, etc, then the risk is lessened on changing the issue type.

It can be done manually for issues that use the same workflow, through the breadcrumbs.

Similarly it can be done in an Automation Rule using the Edit action.

Do you want this to happen only when a new item is created and simultaneously linked to an issue? Or do you want it to happen whenever items are linked together?

If only when a new item is created and simultaneously linked then you could use the Item Created trigger. Include a Condition to check if Linked Items exist.

You might also want to confirm there is only one Linked item. Otherwise how would you instruct the rule to determine the new item type? You can do that by using the Lookup Issues action to execute a JQL to search for items linked to the trigger issue. Then use a Smart Value Condition to confirm that {{lookupIssues.size|0}} equals 1.

Then Edit the trigger issue Type using a smart value to get the Type of the one issue found by the Lookup.