Content
View differences
Updated by Judith Roth 4 months ago
There are some differences between our project identifiers and Jira's jira's project keys:
<figure class="table op-uc-figure_align-center op-uc-figure"><table class="op-uc-table"><tbody><tr class="op-uc-table--row"><td class="op-uc-table--cell" colspan="1" rowspan="1"><p class="op-uc-p"><strong>OP project identifiers</strong></p></td><td class="op-uc-table--cell" colspan="1" rowspan="1"><p class="op-uc-p"><strong>Jira project keys (</strong><a class="op-uc-link" href="https://confluence.atlassian.com/adminjiraserver/editing-a-project-key-938847080.html"><strong>link</strong></a><strong>)</strong></p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell" colspan="1" rowspan="1"><p class="op-uc-p">lowercase</p></td><td class="op-uc-table--cell" colspan="1" rowspan="1"><p class="op-uc-p">uppercase</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell" colspan="1" rowspan="1"><p class="op-uc-p">1-100 characters</p></td><td class="op-uc-table--cell" colspan="1" rowspan="1"><p class="op-uc-p">2-10 characters per default, but maximum can be globally configured and can be more than 100 characters!</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell" colspan="1" rowspan="1"><p class="op-uc-p">a-z, numbers, dashes, underscores</p></td><td class="op-uc-table--cell" colspan="1" rowspan="1"><p class="op-uc-p">A-Z, numbers, underscores</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell" colspan="1" rowspan="1"><p class="op-uc-p">must start with a lower case letter</p></td><td class="op-uc-table--cell" colspan="1" rowspan="1"><p class="op-uc-p">must start with 1 or 2 (uppercase) letters</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell" colspan="1" rowspan="1"><p class="op-uc-p">is used for customizing the URL</p></td><td class="op-uc-table--cell" colspan="1" rowspan="1"><p class="op-uc-p">the URL can be customized and can be different than the project key</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell" colspan="1" rowspan="1"><p class="op-uc-p"><br data-cke-filler="true"></p></td><td class="op-uc-table--cell" colspan="1" rowspan="1"><p class="op-uc-p">the <a class="op-uc-link" href="https://confluence.atlassian.com/adminjiraserver/changing-the-project-key-format-938847081.html">project key format can be changed</a> (but I didn't find the setting in our instance)</p></td></tr></tbody></table></figure>
Most important differences:
* We support dashes, Jira jira don't
* Ours are limited to 100 characters (which is too long for useful semantic work package identifiers)
* Jiras are limited to 10 characters by default but could be configured even to be more than 100 characters
**Questions:**
* Do we keep lowercase or do we migrate to upcase? Or will we decide per usecase (e.g. url downcase, within a semantic id upcase)?
* Do we want to enforce a character limit for project identifiers when semantic IDs ids are used? => yes, we want to enforce this
* Do we want to permit dashes within project identifiers when semantic IDs ids are used? => no, we want to enforce no dashes
<figure class="table op-uc-figure_align-center op-uc-figure"><table class="op-uc-table"><tbody><tr class="op-uc-table--row"><td class="op-uc-table--cell" colspan="1" rowspan="1"><p class="op-uc-p"><strong>OP project identifiers</strong></p></td><td class="op-uc-table--cell" colspan="1" rowspan="1"><p class="op-uc-p"><strong>Jira project keys (</strong><a class="op-uc-link" href="https://confluence.atlassian.com/adminjiraserver/editing-a-project-key-938847080.html"><strong>link</strong></a><strong>)</strong></p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell" colspan="1" rowspan="1"><p class="op-uc-p">lowercase</p></td><td class="op-uc-table--cell" colspan="1" rowspan="1"><p class="op-uc-p">uppercase</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell" colspan="1" rowspan="1"><p class="op-uc-p">1-100 characters</p></td><td class="op-uc-table--cell" colspan="1" rowspan="1"><p class="op-uc-p">2-10 characters per default, but maximum can be globally configured and can be more than 100 characters!</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell" colspan="1" rowspan="1"><p class="op-uc-p">a-z, numbers, dashes, underscores</p></td><td class="op-uc-table--cell" colspan="1" rowspan="1"><p class="op-uc-p">A-Z, numbers, underscores</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell" colspan="1" rowspan="1"><p class="op-uc-p">must start with a lower case letter</p></td><td class="op-uc-table--cell" colspan="1" rowspan="1"><p class="op-uc-p">must start with 1 or 2 (uppercase) letters</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell" colspan="1" rowspan="1"><p class="op-uc-p">is used for customizing the URL</p></td><td class="op-uc-table--cell" colspan="1" rowspan="1"><p class="op-uc-p">the URL can be customized and can be different than the project key</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell" colspan="1" rowspan="1"><p class="op-uc-p"><br data-cke-filler="true"></p></td><td class="op-uc-table--cell" colspan="1" rowspan="1"><p class="op-uc-p">the <a class="op-uc-link" href="https://confluence.atlassian.com/adminjiraserver/changing-the-project-key-format-938847081.html">project key format can be changed</a> (but I didn't find the setting in our instance)</p></td></tr></tbody></table></figure>
Most important differences:
* We support dashes, Jira
* Ours are limited to 100 characters (which is too long for useful semantic work package identifiers)
* Jiras are limited to 10 characters by default but could be configured even to be more than 100 characters
**Questions:**
* Do we keep lowercase or do we migrate to upcase? Or will we decide per usecase (e.g. url downcase, within a semantic id upcase)?
* Do we want to enforce a character limit for project identifiers when semantic IDs
* Do we want to permit dashes within project identifiers when semantic IDs