| Key: |
QB-2840
|
| Type: |
Improvement
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
max1234
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 05/Nov/16 06:28 AM
Updated: 09/Nov/16 06:52 AM
|
|
| Component/s: |
None
|
| Affects Version/s: |
6.1.30
|
| Fix Version/s: |
6.1.31
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
|
Would it possible to have an entry called ANY or ALL that can be mentioned to allow any status to be made as part of the release being created.
Issue is that Jira workflows and status are maintained by separate admins and when they introduce new statuses, the job runs but as status is not in the finite list provided to QB, the fix version is not updated.
|
|
Description
|
Would it possible to have an entry called ANY or ALL that can be mentioned to allow any status to be made as part of the release being created.
Issue is that Jira workflows and status are maintained by separate admins and when they introduce new statuses, the job runs but as status is not in the finite list provided to QB, the fix version is not updated.
|
Show » |
| There are no comments yet on this issue.
|
|
Jira Version creation and management - any status release