Epic import status take over import instead of workflow

Eric Roetenberg
Contributor
March 6, 2024

We get Epic's offered in jira from another system, these may have a different status as the status indicated by the Workflow in Jira
See example: all epics get the status ideeën verzamelen . Can we also make this variable by e.g. executing a Validator or a Post Function in the Workflow.
If e.g. the user = xxxx then take the value as it is in the import instead of the workflow value (status)

 

workflow epic.JPG

1 answer

0 votes
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 6, 2024

Hi Eric,

Not sure if this is what you are asking, but you can add the Status field to the CSV file when you import. 

Eric Roetenberg
Contributor
March 11, 2024

Hi John,

 

This is also what we do with the import, but Jira sees this as a new issue and so always gives the first status and not the status from the import

John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 11, 2024

So you are just doing an update and not a create? 

It's probably that there is not a valid transition between the current status and the new one. I would modify the workflow to add an ALL transition to every status. Then add a Condition so that only the person doing the import is able to execute the transitions. That way no one else sees them while you are doing the process. 

Eric Roetenberg
Contributor
March 11, 2024

Hi John,

do you have an example of such a condition

 

John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 21, 2024

Just add a condition based on a group (like jira-admins which is what I do) then make sure the person who is doing the import is in that group. Or you could do a specific project role that would only have one person in that role for the project and add that project role to the Condition. 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events