[BSERV-4924] Jira issue parsing in Stash commit

Type: Bug
Resolution: Fixed
Priority: Low
Fix Version/s: 3.2.0
Affects Version/s: None
Component/s: Integration - JIRA
Labels:
None

Bug Fix Policy:
View Atlassian Server bug fix policy

My colleague did a commit with message:
"...EURUSD SP-3M swap..."
And since this contained a SP-3 Stash said this was a commit for Project SP and issue 3. This shows two different problems:

1. Stash ignored the trailing M from the message and parsed it anyway
2. There are no Project SP in our Jira (so no issue SP-3). Stash shouldn't parse this if no such issue exists

- - Sort By Name
  - Sort By Date
  - Ascending
  - Descending
  - Thumbnails
  - List

incorrect issue number.png
5 kB
01/Jul/2014 10:51 AM

relates to

BSERV-2470 JIRA Integration: Check for issue validity before linking issues

Closed

BCLOUD-20644 JIRA Integration: Check for issue validity before linking issues

Gathering Interest

FUSE-1257 Failed to load

mentioned in: Page Failed to load

Ijeoma Ekeh made changes - 03/Dec/2020 6:26 AM

Link

New: This issue relates to BSERV-12680 [ BSERV-12680 ]

Owen made changes - 10/Apr/2019 6:47 AM

Workflow

Original: Stash Workflow - Restricted [ 1447321 ]

New: JAC Bug Workflow v3 [ 3136148 ]

Owen made changes - 07/Jul/2016 4:04 AM

Workflow

Original: Stash Workflow [ 698151 ]

New: Stash Workflow - Restricted [ 1447321 ]

Roger Barnes (Inactive) made changes - 19/Oct/2015 5:39 AM

Remote Link

Original: This issue links to "Page (Extranet)" [ 72617 ]