The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Assign issues to calculated sprints in jira not working

jo-ma
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 4, 2018

Hi,

 

I use Portfolio 2.17. We have calculated fix versions and calculated sprints on most of our stories and epics. 

We want to propagate this back to jira. I followed the "Assigning issues to sprints": https://confluence.atlassian.com/jiraportfoliocloud/assigning-issues-to-sprints-828785264.html

From Scope view: I see I can manually re-select the calculated sprint value. This is a high effort for each and every story or epic. Seems not to be practical.

 

From Timeline view: 

The sprint is in jira, issue as well. Each story is only in one sprint, issues are not already assigned to sprint, calculate is done etc.

If I click in the timeline to the sprint, I can see the statistic free capacity, planned capacity, capacity utilization, but I can't see the assign 2 calculated issues.

 

 

1 comment

Comments for this post are closed

Community moderators have prevented the ability to post new comments.

Glen Schumacher
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 6, 2018

Hello, I had this same problem.  You need to have the schedule settings (the little gear icon in the upper right corner) set to group by team or person.  You should be able to sync back to JIRA then.  I have no idea why this is needed, but it works!

TAGS
AUG Leaders

Atlassian Community Events