Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,458,383
Community Members
 
Community Events
176
Community Groups

Sub-task Dependencies in Portfolio 2.0

I found a defect in new version of Portfolio that impacts its use if the teams are using sub-tasks in JIRA

The defect is exposed in two ways:
1) If the sub-tasks have dependencies upon one another, Portfolio will not schedule the story.
2) If the sub-tasks do not have dependencies upon one another, Portfolio will schedule the resources concurrently.
Example:
  • There is a story with three sub-tasks: Design (2 days), Develop (3 days) and Test (4 days).
  • If the sub-tasks are set up so that design blocks development and development blocks testing, Portfolio will not schedule the story and produce errors that there is a violation in dependencies and cyclic dependency detected.
  • If the dependencies are removed, Portfolio will schedule all the resources concurrently. In this example, that would make it appear the designer is working on the story for 9 days and that all resources will start working on the story on the same day.
  • The setting 'Issue assignee import level' in configuration does not address this.
I communicated this to Atlassian and they have logged it as a suggestion.

8 answers

I found the record in Atlassian's instance - https://jira.atlassian.com/browse/JPO-1600

Currently, this is listed as a Suggestion and is not assigned.  

Same issue with me. Any workaround in place?

Hitting the same issue, I even tried removing "Block" linktype as a Portfolio dependency linkype but it still complains about cyclic dependency error.

 

I have not heard back from Atlassian on this. 

Any updates/guidance on this as I am also getting this error and am not able to link 2 Sub-tasks.

I encounter the exact same issue here.

in my test setup I have a 

task "testtask" with two subtasks task1 and task2, where task1 blocks task2 (so definitely NOT a cyclic dependency)

 

I also get the "Cyclic dependency detected. "error with a red exclamationmark

Hi Eric,

I have not heard back from Atlassian on the stats of the defect and the respondent from Atlassian, rchristian@atlassian.com, did not provide a defect ID. sad

Thanks,

Marie

Do you know what the defect ID is? I believe I am seeing this same issue.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events