Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
0
-
3
-
Description
NOTE: This suggestion is for JIRA Portfolio Server. Using JIRA Portfolio Cloud? See the corresponding suggestion.
The 'Cyclic Dependency' error in Portfolio for JIRA points out when dependency links have been set up incorrectly in JIRA.
As a result of detecting this error the tool will then not schedule the work at all (which is probably correct), but there is very little information on the error to go on, which results in a lot of manual searching through JIRA.
If, for example, you have a cyclic dependency on a couple of stories, the error will appear on those stories AND the parent Epic AND all of the stories in that Epic AND anything else that may be linked to the Initiative above it. This means when you are viewing the Initiative you know there is an error somewhere underneath, but you have to go through every Epic and Story in turn to find the problem, which is very time-consuming.
It is a user error, but it would be very helpful if the error/warning could direct you to the offending issues, either diagrammatically or textually.
Attachments
Issue Links
- is duplicated by
-
JSWSERVER-24944 Violation dependency should be explained - display which issue could not be scheduled
- Gathering Interest
- relates to
-
JSWCLOUD-19442 Cyclic dependency error should provide more information
- Gathering Interest