When moving issue to a different issue type, force the status to create transition status

[Ajay Prasad]

Want to figure out if there is a way to force the status during the "move" of an issue.

Here is my scenario :

We have a sub task in the "In Progress" status. When this particular sub task is moved to a "Story", the user is able to retain the status.

However, when a story is created using create issue, the story gets the status "new" which is then at some point transitioned to In Progress.

I am interested in making sure that when a story is created using the "move" approach, system forces the status to be "New".

[Angélica Luz]

Hi Ajay,

Currently, it's not possible to force the change of status while moving an issue.
We have a feature request suggesting the implementation of this ability:
- https://jira.atlassian.com/browse/JRACLOUD-5159
Please, click on vote and watch to receive updates about the feature.

As per our documentation "Moving an issue":

You may have set up custom issue statuses as part of a workflow. If you have assigned a custom status to your issue, and it does not exist in your target project, you must select a new issue status for your issue. You cannot arbitrarily change the issue status, i.e. the option to change the issue status will only appear if you are required to change it.

Regards,
Angélica

[Ajay Prasad]

Thanks for the link. This issue has been open for almost 15 years. Is there any possibility that it will get worked on ?

[Angélica Luz]

Hi Ajay,

We don't publish roadmaps with release dates, so we don't know when or if the feature will be implemented. We must wait for our dev team to comment on the feature.

Regards,
Angélica

[Dragos Hazi]

This is really absurd; why would dev team need to comment on the feature, as this is clearly a decision on product level?

Does it make sense to implement or not? (I think comments on that issue outline a serious problem which us, Jira users, have without this enhance). You do need to answer that, especially that it has been raised 18 years go, and either kill the idea (though customers need it) or accept it. But then, if it is important, there is need to put it into some roadmap, even if is for a longer term one. Like this is just in a limbo state where customers are "tricked" when concerns are raised into this regard that "yeah, we have a ticket, vote for it", but nothing happens.