Issue when trying to change Issue Type within a project

[Rafael Freymueller]

Hi everyone,

I am having an issue where I want to change the issue type for an issue.

It is no longer possible to change the issue type directly from the Icon when viewing an Issue. Specifically I want to change a Bug to a Task.

Interestingly, I am able to change a Task into a Bug (by selecting the Icon), but not the other way around.

Through the move function I am still able to change the issue type. However, because the Bug utilizes a different description field than a Task, due to a different template being utilized, the content of the original description field gets lost. 

So my questions would be:

1. Is there a way of restoring the function to directly change the issue type by clicking on the Icon -> from Bug to Task

2. Is there a way to transfer the content of the original description field to the description field of the moved issue? Although they are 2 separate fields, they serve the same purpose. The Bug description just works with a pre-existing template.

I also attached a picture of the existing Screens in case that might be useful information.

Thanks everyone for helping me out on this one!

[Yoann LEGRAND]

Hello @Rafael Freymueller , 

Have you checked that the "Issue Type" field is present on all screens (in this case, the one used by task, as Bug seems OK)?

[Rafael Freymueller]

Thanks that solved the first issue of not being able to change the issue type directly through the Icon!

The only issue left would be that the content of the Bug description is 'lost' / not showing up in the Task after moving it. Would there be some way of implementing an automation for that specific use case? Or any other alternative really.

[Yoann LEGRAND]

"Move" feature keep issue description.
Have you check if field "description" is correctly in the view screen of Bug ?

 If you use another field for Bug description, , Automation can help you : 

1: I copy the description field into my customfield
2: The opposite.

[Rafael Freymueller]

Thanks for the reply!

How would the entire automation chain look like for this function / what would be the trigger?