In my workflow when I move a story back to DEV from QA I have a defect screen that is launched. There is a separate issue type called "Defect" I am using. If I move a "Story" issue type the "Defect" screen is opened however the Issue type is "Story" instead of "Defect" as I would like. What am I doing wrong?
http://confluence.atlassian.com/display/JIRA/Configuring+Project+Keys
Should show you how to achieve this - note it is not recommended to change if you use Greenhopper
can you provide any information about what might go "wrong" if you make a change and you're using greenhopper? I just want to allow numbers in the project key, so I'd use the regex provided in the documentation: ([A-Z][A-Z0-9]+)
In a VERY quick test on a sandbox machine, greenhopper seems OK with this project key, but if you have any specifics about what might not work that'd be helpful. Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We have this modified on our systems and use GH all the time. I haven't seen any issues with it but would be curious what others have seen too
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can't. You can allow numbers and other characters, but a format like LGIT-2011-418 is not valid - you can't safely use the character "-" as part of the project key.
Martin's advice is completely correct, but I'd like to add that you really should not change the format to include anything that might be a control character. The regular expression actually lets you put in -, ? and & for example, but they all break things. I wouldn't allow anything more complex than (<tt>[A-Z][A-Z0-9]+</tt>) (First character A-Z, the rest A-Z,0-9)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Fully support all that Nic says here. The wiki page does outline that the 'dash' character should not be used, amongst others. So should enable you to make an informed decision.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.