-
Suggestion
-
Resolution: Unresolved
Summary
Jira used to be more relaxed and allow the underscore character to be present in Jira project keys, which has since been removed. Fisheye/Crucible still support the old standard. This update would allow Fisheye/Crucible to match Jira's documentation and would match the current Jira standard for issue keys.
Jira's current Standard:
"The default Jira key format – that is, two or more uppercase letters ([A-Z][A-Z]+), followed by a hyphen and the issue number."
Current Behavior
If a Jira issue key is placed in a review's title, the below will occur:
"Title to Crucible review_ABC-123"
Actual Jira issue key: ABC-123
What Crucible will parse and think is the issue key: review_ABC-123
- is related to
-
FE-6687 Jira issue development panel shows wrong commits
-
- Long Term Backlog
-
[FE-7150] Update Jira Issue project key formats to reflect Jira's more restrictive default
| Status | Original: Gathering Interest [ 11772 ] | New: Not Being Considered [ 11776 ] |
| Fix Version/s | New: N/A [ 54414 ] | |
| Labels | New: jac-cleanup-phase10 |
| Workflow | Original: JAC Suggestion Workflow [ 3079914 ] | New: JAC Suggestion Workflow 3 [ 3642017 ] |
| Component/s | New: Integrations [ 12293 ] |
| Description |
Original:
h3. Summary
Jira used to be more relaxed and allow the underscore character to be present in Jira project keys, which has since been removed. This update would allow Fisheye/Crucible to match Jira's documentation and would match the current Jira standard for issue keys. h3. [Jira's current Standard|https://confluence.atlassian.com/jirasoftwareserver0711/referencing-issues-in-your-development-work-955166285.html]: "The default Jira key format – that is, two or more uppercase letters ([A-Z][A-Z]+), followed by a hyphen and the issue number." h3. Current Behavior If a Jira issue key is placed in a review's title, the below will occur: "Title to Crucible review_ABC-123" Actual Jira issue key: ABC-123 What Crucible will parse and think is the issue key: review_ABC-123 |
New:
h3. Summary
Jira used to be more relaxed and allow the underscore character to be present in Jira project keys, which has since been removed. Fisheye/Crucible still support the old standard. This update would allow Fisheye/Crucible to match Jira's documentation and would match the current Jira standard for issue keys. h3. [Jira's current Standard|https://confluence.atlassian.com/jirasoftwareserver0711/referencing-issues-in-your-development-work-955166285.html]: "The default Jira key format – that is, two or more uppercase letters ([A-Z][A-Z]+), followed by a hyphen and the issue number." h3. Current Behavior If a Jira issue key is placed in a review's title, the below will occur: "Title to Crucible review_ABC-123" Actual Jira issue key: ABC-123 What Crucible will parse and think is the issue key: review_ABC-123 |
| Description |
Original:
h3. Summary
Jira used to be more relaxed and allow the underscore character to be present in Jira project keys, which has since been removed. This update would allow Fisheye/Crucible to match Jira's documentation and would match the current Jira standard for issue keys. h3. [Jira's current Standard|https://confluence.atlassian.com/jirasoftwareserver0711/referencing-issues-in-your-development-work-955166285.html]: "the default Jira key format - that is, two or more uppercase letters ([A-Z][A-Z]+)" h3. Current Behavior If a Jira issue key is placed in a review's title, the below will occur: "Title to Crucible review_ABC-123" Actual Jira issue key: ABC-123 What Crucible will parse and think is the issue key: review_ABC-123 |
New:
h3. Summary
Jira used to be more relaxed and allow the underscore character to be present in Jira project keys, which has since been removed. This update would allow Fisheye/Crucible to match Jira's documentation and would match the current Jira standard for issue keys. h3. [Jira's current Standard|https://confluence.atlassian.com/jirasoftwareserver0711/referencing-issues-in-your-development-work-955166285.html]: "The default Jira key format – that is, two or more uppercase letters ([A-Z][A-Z]+), followed by a hyphen and the issue number." h3. Current Behavior If a Jira issue key is placed in a review's title, the below will occur: "Title to Crucible review_ABC-123" Actual Jira issue key: ABC-123 What Crucible will parse and think is the issue key: review_ABC-123 |
| Description |
Original:
h3. Summary
Jira used to be more relaxed and allow the underscore character to be present in Jira project keys, which has since been removed. This update would allow Fisheye/Crucible to match Jira's documentation and would match the current Jira standard for issue keys. h5. [Jira's current Standard|https://confluence.atlassian.com/jirasoftwareserver0711/referencing-issues-in-your-development-work-955166285.html]: "the default Jira key format - that is, two or more uppercase letters ([A-Z][A-Z]+)" h5. Current Behavior If a Jira issue key is placed in a review's title, the below will occur: "Title to Crucible review_ABC-123" Actual Jira issue key: ABC-123 What Crucible will parse and think is the issue key: review_ABC-123 |
New:
h3. Summary
Jira used to be more relaxed and allow the underscore character to be present in Jira project keys, which has since been removed. This update would allow Fisheye/Crucible to match Jira's documentation and would match the current Jira standard for issue keys. h3. [Jira's current Standard|https://confluence.atlassian.com/jirasoftwareserver0711/referencing-issues-in-your-development-work-955166285.html]: "the default Jira key format - that is, two or more uppercase letters ([A-Z][A-Z]+)" h3. Current Behavior If a Jira issue key is placed in a review's title, the below will occur: "Title to Crucible review_ABC-123" Actual Jira issue key: ABC-123 What Crucible will parse and think is the issue key: review_ABC-123 |