Question: Create Issue Group or Set Fields

[Nico Harold]

This may not be possible but I had asked Atlassian in the past for my needs and they did not have a solution within JIRA. Is it possible to have one of your Post-Functions write to multiple fields based on a condition? Or is it possible to create a set of Issues when a specific Issue is created? I will explain below:

So the way our group documents releases we have certain individual documentation requirements, as we operate in a highly regulated environment, which I create as a set of documentation tasks on each release. What I had asked Atlassian in the past was if there was an Issue Macro that I could fire off and just fix what version the set of issues would belong to and create all these issues in a couple of clicks rather than creating the same set of issues for every release manually.

What I was investigating was to see if your Add-in on Issue creation could do one of the following:

• Use the Copy Parsed Text to a Field Post-Function upon issue creation but have it set multiple fields conditioned on my inputting a very specific Summary text. Example: I create an issue and input ASR in the Summary field and fix my version to the issue. Then the Post-Function would update Summary to Application Security Review, set issue type to Approval, set priority to Blocker, set description to what the ASR must do, and set the Assignee to our Application Security Engineer.

• OR the best solution would be if I create a single issue for myself meeting certain conditions, and I fix the version to it, then a set of issues would be created, one for each documentation requirement with the fields set and assigned appropriately with the fix version copied to each of them. Then I would only have to create one issue.

Again not sure if it is even possible but figured I'd ask. A create a issues macro, or set fields macro would be a pretty cool Post-Function.

[Fidel Castro Armario]

Hi @NFALZONE,

You can easily implement your best solution (i.e., the second one) using "Create issues and subtasks" post-function.

In your case I think that you should use multiple issue creation using seed strings like in the following examples:

• Create a Story for each Component in Epic
• Create 3 Stories in an Epic
• Create a Sub-task for each User selected in a Multi-User Picker
• Create specific Sub-tasks for each selected Components

Specially, if you always create the same set of documents you should use a solution like the one described in example: Create 3 Stories in an Epic.

Please, let me know if you have any doubt on how to do it.

[Nico Harold]

Thanks that worked great! One additional question/request, is it possible to change the Issue Type for each Sub-Task? Right now I set up it to create my Issues as type "Documentation" in our system however I have to go back after they're created and change one to type "QA" and one to "Approval". If not no worries, it only takes me a couple of seconds to change those.

[Fidel Castro Armario]

Each "Create issues and subtasks" post-function can create only one issue type.

If you want to create different issue types, no problem, you should use one "Create issues and subtasks" post-function for each issue type.