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!
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...)
I have a same requirement to unset assignee when you clone but i don't see "Clear Field Value" in post function. Can you please help?
error.JPG
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hey steve.
right now i only got one idea
https://marketplace.atlassian.com/plugins/org.swift.jira.clone-plus
but i will try to find a free solution...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
agree. i will try to dig more into this..
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for that. For this single use case these costs are way to expensive, though.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@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.
@Natalie Hobson
Hehe, yes I did that! :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Just a check - did you remember to publish the workflow before trying it out?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Welcome to great meetings, with less work. Automatically record, summarize, and share instant recaps of your meetings with Loom AI.
Learn moreOnline forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.