You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We have cross project dependencies and we want story level releases or at-least have control on releases of tasks of a story, that is, tasks cannot be released unless DEMO/UAT of the story is approved.
So with story of project A and tasks are spread across different projects A, B, C & D.
Can portfolio allow control on story level releases.
Hi Charu,
You could use Tasks instead of Sub-Tasks and create issue links between the Tasks and Story. The Tasks can be in different Projects. Using the issue links, Portfolio will at least warn you about scheduling conflicts.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.