| Key: |
QB-2812
|
| Type: |
Bug
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Minor
|
| Assignee: |
Unassigned
|
| Reporter: |
Benoit Maury-Bouet
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 23/Sep/16 01:53 PM
Updated: 27/Sep/16 06:36 AM
|
|
| Component/s: |
None
|
| Affects Version/s: |
6.1.23
|
| Fix Version/s: |
6.1.27
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
|
Dear all,
I think there is a small in the jira progression.
We have a submit assistant that formated scm changes this way:
[TAG][COMPONENT][fix JIRA-123,JIRA-234] some change ..
When commiting this we could see the jira issues in QB dashboard but our update step didn't work
replacing adding space before "fix" command and after the jira list seems to fix the issue...
so for instance [TAG][COMPONENT][ fix JIRA-123,JIRA-234 ] some change .. will work
I tried different regex engines but even if I force word boundaries around "fix" or the jira ids the regex still works.
Thanks
|
|
Description
|
Dear all,
I think there is a small in the jira progression.
We have a submit assistant that formated scm changes this way:
[TAG][COMPONENT][fix JIRA-123,JIRA-234] some change ..
When commiting this we could see the jira issues in QB dashboard but our update step didn't work
replacing adding space before "fix" command and after the jira list seems to fix the issue...
so for instance [TAG][COMPONENT][ fix JIRA-123,JIRA-234 ] some change .. will work
I tried different regex engines but even if I force word boundaries around "fix" or the jira ids the regex still works.
Thanks
|
Show » |
| There are no comments yet on this issue.
|
|
Jira issues not progressed under certain circumstances