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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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

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

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

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

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

I have not heard back from Atlassian on this. 

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

 

Same issue with me. Any workaround in place?

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.  

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Advanced Roadmaps

3 short videos to help you get started with Advanced Roadmaps

Hi community, I’m Roi, a product manager working on Advanced Roadmaps for Jira. While Advanced Roadmaps is a powerful tool to plan and track work at scale, we know it can be challenging to get star...

6,584 views 25 19
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you