Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Update issue types - How to make sure the form reacts on changing the issue type

Nanda Kops-Assendelft
Contributor
October 5, 2018

I created several subtasks. All have the same fields, expect for one (let's call it subtaks X). I've created two schemes: one for subtask X and one for all the others. Works all fine. I create subtask <> X, all available fields correspond with my configuration. Create subtask X, some more fields are available. Perfect so far.

 

But the problem is, editing these subtasks and then especially the issue type itself. So when I edit subtask <> X to issue type subtask X, I want to be able to edit the extra fields which belong to subtask X. And the other way around, when I want to edit the subtask X to another issue type, less fields are available.

So the form doesn't realy react on changing the issue type by displaying more (or less) fields on the form.

Should I not allow issue type to be changed? Or is it possible that the form reacts directly when changing the issue type.

Or maybe you need something like the functionality convert issue to subtask....

0 answers

Suggest an answer

Log in or Sign up to answer