I've got the following questions:
1. Is it (safely) possible to rename the default Greenhoppers issue types (i.e. "Technical Task" into "Task", "User Story" into "Requirement")?
2. If yes, how can I do this? I can't find the form to do this. (I'm using Jira 4.3 with Greenhopper)
3. If no, I would like to create new Issue Types and -schemes. Are there any restriction when using Greenhopper with custom issue types?
Thanks a lot.
There already is a Task issue type, so you won't be able to have a second issue type with the same name.
I would (a) make a copy of the GreenHopper Issue Type Scheme, (b) create a new issue type for Requirement, and (c) adjust the new issue type scheme to use Task instead of Technical Task and Requirement instead of Story.
The only thing to be careful with using a non-standard issue type scheme with GreenHopper is if you want to use the Scrum Template. You can read about it here: http://confluence.atlassian.com/display/GH/Specifying+your+Project+Templates#SpecifyingyourProjectTemplates-Aboutthe%27Scrum%27Template
Thank's for your reply. I only found the possibility for renaming Issue Types globally ("Manage Issue Types -> Global Issue Types") so far.
But we have several projects running. That's why I created my own Issue Type Scheme to be used with my Project. Unfortunatly I can't find the rename Issue Type option within the "Modify Issue Type Scheme" form. How can I do this?
Over the next several weeks we'll be sharing some of our Getting Started guides here in the community. Throughout this series of posts, we'd love to hear from customers and non-customers ab...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs