Cloning issues

[Jon]

Hi,

When i clone an issue it duplicates everything except the status. is there anyway to make it clone as the same status as the original issue that is cloned? 

Another question is there a way to make rules on the status. such as if XX field is not entered it cannot be in XX status. and if a field was ever removed it would automatically give an error message that the status is not acceptable because XX field is not filled in. 

thanks

jon

[Alexey Matveev]

Hello,

1. You can not set a status by cloning an issue. You would need an add-on like Power Scripts or ScriptRunner to make your own script.

2. You can use a validator for the transition. Go to the workflow configuration, find the required transition and have a look if you any of the validators match your requirement. For example, you can try the Field Required Validator. It would not let you move and issue to another status. 

Concerning removing a value, you can try to do it with Power Scripts Live Fields or ScriptRunner behaviours

[Cristian Rosas [Tecnofor]]

Please, try to not repeat questions:

https://community.atlassian.com/t5/Jira-questions/Cloning-issues-and-getting-the-same-status-on-the-new-issue-type/qaq-p/845621

Answering to the other part of the question, there are some ways to achieve this:

You can add validators in your transitions to not allow to advance if that field is not filled. Also, do not put that field in the edit screen so it can't be erased and make transitions to edit this field. Another way is to make it mandatory and add a value like "this is empty or whatever" if you need it in the edit screen, or you can use behaviours (I saw in another post that you have ScriptRunner).

If you do the second, remember that this will affect your reports as that field can't be empty