Changing Issue Type Scheme

[Oliver Jones]

Hi there,

I've been requested to make major changes to a projects fields / issue type scheme which I've been preparing on a test board. The main board is extremely busy with hundreds of live issues which cannot lose the existing data.

The question I have is will applying the new fields/scheme to the main project cause any problems with the existing open issues? Lots of the existing fields have been changed and data loss on existing tickets would cause severe problems.

Thanks in advance.

[Trudy Claspill · Accepted solution]

Yes, changes to the field configurations, field configuration schemes, and issue type scheme likely will affect existing issues, if any of the changes you make apply to the issue types and fields already in the project.

[Eldad Dayagi]

Hi @Trudy Claspill 

I'd appreciate your help also.

I just opened a new project, it got its own default issue type scheme with all the standard issue types (epic, story, bug, task, sub task).

Do I have to worry about other projects being affected if I for example add another issue type to the issue type scheme of this newly opened project? I am guessing the answer is no.

Also, let's say that I'll leverage an existing issue type scheme from another project, what should I do with the issue type scheme that was created for my project? remove it? will this affect anything, even if this is the only project that was using this issue type scheme?I am guessing the answer here is also is no.

Thanks so much,

Appreciate it

[Trudy Claspill]

@Eldad Dayagi

Please start a new Question in the community to get assistance with your issue.

Posting a question on a post that is over a year old and has an Accepted Answer is generally considered poor community etiquette.