nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

unset assignee in create transition (of cloned issue)

skorzinetzki

Use Case:

Cloned issues have cloned the assignee, but they should come up as not assigned.

Solution approach:

I want to unset the assignee in the create transition, because there is no special clone step or event.

For this, I created a post-function in the create transition. It is the update issue field post-function and selected "assignee" as field and "not assigned" as value.

Problem:

I positioned it after any existing post-function. No matter where, it does not work.

What am I doing wrong? Do you have another solution approach? Jira-Version is: 4.4!

Thank you!

error.JPG

Accepted answers

skorzinetzki

Now I have a new use case with same requirement, so I tried again...
And I found a solution:

Last time I used "Update Issue Field", which is a post function of a plugin.

Now I used "Clear Field Value" post function, which works!

(Shame on me...)

All comments

Nadir MEZIANI

I think that this link can help you to autorize unassigned issue.

https://confluence.atlassian.com/display/JIRA/How+do+I+assign+issues+to+multiple+users

Good Luck

Natalie Hobson

Just a check - did you remember to publish the workflow before trying it out?

skorzinetzki

I found this answer: https://answers.atlassian.com/questions/29053/clearing-fields-on-cloned-issues-during-cloning-action

This tells exactly that this way (post-function in create transition) should work. Maybe I will have look at the logs... -> nothing in here...

skorzinetzki

@zezeto

Thank you for this suggestion, our jira instance was already configured to allow unassigned issues. This is even the default case for this specific project.