When trying to rename Issue Types, JIRA forces you to change field values

[forums-5]

Greetings all,

I have two issue types, let's call them "Foo" and "Bar", in my current Issue Type Scheme.  I need to rename them to "Foo Request" and "Bar Enhancement", respectively, but only in a particular project.  I Added the new issue types and cloned the existing schema, then edited the schema to remove the two old names and add the two new schemes.

Predictably, I am presented with a "Issue Type Migration" wizard.  This is great.  I am asked "What do you want issues of this type to be migrated to?" and I select the new type - everything is great, right?  Alas, not so much.

The next page says "Update fields for issues with current issue type 'Foo' in project 'myProject'", and it requires me to enter an Assignee and Reporter.  There are checkboxes next to these for "Retain previous value" but it FORCES you to enter a new value.

I am not confident that it won't overwrite or change 1000+ issues with bad data.  How can I be sure?  Has anyone done this before?  Is it safe to do this migration?  Why does it require me to enter a value when I am retaining the old one?
--
Post by cmyers - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=38373
_______________________________________________
Jira-user mailing list
Jira-user@...
To unsubscribe or change your options visit this page:
http://lists.atlassian.com/mailman/listinfo/jira-user

[forums-5]

Just to add, I tried to repro the problem in a test project I created but with a handful of issues, with various assignees (and all reported by me) this behavior does not happen.

Instead, I just get a yellow "warning" box that says "all field values will be retained", no text entry, no checkboxes.  Screenshots attached.

The "real" project where I see the problem has over 1000 issues of these types, and may include issues assigned to or reported by people who have left the company, so that is my only guess for what is going on, but I need a solution to make this change without risking assigning 1000+ issues to a single person and losing all of that metadata.

Thanks!
-Carl
--
Post by cmyers - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=38373
_______________________________________________
Jira-user mailing list
Jira-user@...
To unsubscribe or change your options visit this page:
http://lists.atlassian.com/mailman/listinfo/jira-user

[forums-5]

bump -  I would still really appreciate an answer from Atlassian for this....

Thanks!
--
Post by cmyers - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=38373
_______________________________________________
Jira-user mailing list
Jira-user@...
To unsubscribe or change your options visit this page:
http://lists.atlassian.com/mailman/listinfo/jira-user

[forums-5]

Atlassian don't always respond here.  If you really need their help, raise a support request.

However...

>The next page says "Update fields for issues with current issue type 'Foo' in project 'myProject'", and it requires me to enter an Assignee and Reporter. There are checkboxes next to these for "Retain previous value" but it FORCES you to enter a new value.

Um, actually, it's not Jira forcing you, it's your settings.  If you look at the field configuration scheme for the project, I think you'll find Reporter and Assignee are mandatory.

>I am not confident that it won't overwrite or change 1000+ issues with bad data. How can I be sure? Has anyone done this before? Is it safe to do this migration?
Yes, use the retain, I must have clocked up hundreds of thousands by now.  *But*, I always test it in a dev/test copy and run it past my users.  Often with large downloads to Excel and some manual "if column A in sheet 1 <> column A in sheet 2" type formula to help me compare.


>Why does it require me to enter a value when I am retaining the old one?
Assignee and Reporter are a little complex - you may have reporter and assignee permissions where one of them is someone who has been removed from the permissions that allow them to be set


To be honest, when I do these sort of migrations, I cheat:
*  I set up a permission scheme with reporter and assignee permissions for "anyone".
*  I make sure that Jira is set to allow unassigned issues.
*  I set up a field config scheme where absolutely no fields are set as mandatory.

Then I apply them to the project, do the edit, and put the old settings back...
--
Post by broughn2 - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=38373
_______________________________________________
Jira-user mailing list
Jira-user@...
To unsubscribe or change your options visit this page:
http://lists.atlassian.com/mailman/listinfo/jira-user