Copy Page

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account. You can also Sign Up for a new account.

We want project names like data.finger-tree and test.benchmark. JIRA project names can do this, but project keys can't: by default they are instance-unique, uppercase alpha only.

You can <a href="http://confluence.atlassian.com/display/JIRA/Configuring+Project+Keys">change JIRA's rules</a> for project keys, but
<ul>
	<li>There is a strict warning against allowing a dash. (Tools use dash to separate project key from issue number).</li>
	<li>It is not easy to do (you have to shutdown JIRA, change properties, possibly rebuild webapp).</li>
	<li>Changes to legal JIRA keys must be <a href="http://docs.marvelution.com/display/MARVJIRAHUDSON/Using+non-standard+Jira+Project+and+Issue+keys">manually propagated</a> into other systems, e.g. Hudson, which do not treat JIRA keys as opaque.</li>
</ul>

Amusingly, renaming from one key to another is <a href="http://confluence.atlassian.com/display/JIRA/Changing+the+Project+Key">also difficult</a>, and breaks links. So changing your mind later is not so good.

Options
<ul>
	<li>names like TESTBENCHMARK (spell out category and lib)</li>
	<li>names like BENCH (abbreviate lib only, with possible collision problems later)</li>
	<li>names like TBENCH (abbreviate category and lib)
	<ul>
		<li>RH - yes, first character of parent and first 5 characters of name
		<ul>
			<li>TBENCH</li>
			<li>DFINGE</li>
		</ul>
		</li>
	</ul>
	</li>
	<li>modify JIRA's rules and face the consequences above</li>
</ul>