-
Suggestion
-
Resolution: Duplicate
-
None
-
1
-
Currently, if a status is mapped to "done" in JIRA but doesn't have a resolution post function or the workflow associated to the project or issue type removes the resolution on transition, the issue will NOT show in Portfolio, unless the child issue is in progress or to do. It would be nice if Portfolio ignored the resolution date when brining in issues.
Expecting all of our customers to use canned workflows and resolutions on done statuses is very "perfect world JIRA".
We have documentation on this but it is one line:
Any issues that have been marked as done in Jira Software, that don't have a resolution set, will not be included in the plan.
It is confusing for end users and adds technical debt for JIRA admins to open a ticket with Atlassian to run down what the issue might be.
- duplicates
-
- Under Consideration
- relates to
-
- Gathering Interest
-
JPOS-5172 You do not have permission to view this issue
[JPOSERVER-2658] Allow issues with statuses mapped to done without resolutions
| Remote Link | Original: This issue links to "JPOS-5172 (Bulldog)" [ 481308 ] | New: This issue links to "JPOS-5172 (JIRA Server (Bulldog))" [ 481308 ] |
| Resolution | New: Duplicate [ 3 ] | |
| Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
| Link | New: This issue duplicates JPOSERVER-2442 [ JPOSERVER-2442 ] |
| Summary | Original: Allow completed issues without resolutions | New: Allow issues with statuses mapped to done without resolutions |
| Description |
Original:
Currently, if a status is mapped to "done" in JIRA but doesn't have a resolution post function or the workflow associated to the project or issue type removes the resolution on transition, the issue will NOT show in Portfolio, unless the child issue is in progress or to do. It would be nice if Portfolio ignored the resolution date when brining in issues.
Expecting all of our customers to use canned workflows and resolutions on done statuses is very "perfect world JIRA". We have [documentation|https://confluence.atlassian.com/jiraportfolioserver/viewing-work-960719431.html] on this but it is one line: bq. Any issues that have been marked as done in Jira Software, that don't have a resolution set, will not be included in the plan. It is confusing for endusers and adds technical debt for JIRA admins to run this done and then open a ticket with Atlassian to run down what the issue might be. |
New:
Currently, if a status is mapped to "done" in JIRA but doesn't have a resolution post function or the workflow associated to the project or issue type removes the resolution on transition, the issue will NOT show in Portfolio, unless the child issue is in progress or to do. It would be nice if Portfolio ignored the resolution date when brining in issues.
Expecting all of our customers to use canned workflows and resolutions on done statuses is very "perfect world JIRA". We have [documentation|https://confluence.atlassian.com/jiraportfolioserver/viewing-work-960719431.html] on this but it is one line: bq. Any issues that have been marked as done in Jira Software, that don't have a resolution set, will not be included in the plan. It is confusing for end users and adds technical debt for JIRA admins to open a ticket with Atlassian to run down what the issue might be. |
| Description |
Original:
Currently, if a status is mapped to "done" in JIRA but doesn't have a resolution post function or the workflow associated to the project or issue type removes the resolution on transition, the issue will NOT show in Portfolio, unless the child issue is in progress or to do. It would be nice if Portfolio ignored the resolution date when brining in issues.
Expecting all of our customer's to use canned workflows and resolutions on done statuses is very "perfect world JIRA". |
New:
Currently, if a status is mapped to "done" in JIRA but doesn't have a resolution post function or the workflow associated to the project or issue type removes the resolution on transition, the issue will NOT show in Portfolio, unless the child issue is in progress or to do. It would be nice if Portfolio ignored the resolution date when brining in issues.
Expecting all of our customers to use canned workflows and resolutions on done statuses is very "perfect world JIRA". We have [documentation|https://confluence.atlassian.com/jiraportfolioserver/viewing-work-960719431.html] on this but it is one line: bq. Any issues that have been marked as done in Jira Software, that don't have a resolution set, will not be included in the plan. It is confusing for endusers and adds technical debt for JIRA admins to run this done and then open a ticket with Atlassian to run down what the issue might be. |
| Labels | New: pse-request |
| Description | Original: Currently, if a status is mapped to "done" in JIRA but doesn't have a resolution post function or the workflow associated to the project or issue type removes the resolution on transition, the issue will NOT show in Portfolio, unless the child issue is in progress or to do. It would be nice if Portfolio ignored the resolution date when brining in issues. |
New:
Currently, if a status is mapped to "done" in JIRA but doesn't have a resolution post function or the workflow associated to the project or issue type removes the resolution on transition, the issue will NOT show in Portfolio, unless the child issue is in progress or to do. It would be nice if Portfolio ignored the resolution date when brining in issues.
Expecting all of our customer's to use canned workflows and resolutions on done statuses is very "perfect world JIRA". |
| Link | New: This issue relates to JPOSERVER-1405 [ JPOSERVER-1405 ] |
| Remote Link | New: This issue links to "JPOS-5172 (Bulldog)" [ 481308 ] |