Task Spanning Multiple Sprints - How do I Capture Actual End Date?

Marcia

1 task going across 2 - 2 weeks Sprints

Jira is pulling the first Sprint Name, Start and End Date --- but, the Task will not finish until the end of the second sprint.

 

Any suggestions on how to include subsequent Sprints? 

I have attached a screenshot of what came over from Jira to SmartSheet Sprint Name, Start and End Date for the 1st Sprint (From SS.PNG),  what is in Jira in the details section (E52,E53) -- (Jira Details.PNG) and what is in Jira off on the right side of the page (From Jira).

Thanks!

Michael Weiland

Hi Marcia,



Thanks for reaching out! I understand that you have a JIRA Issue assigned to multiple Sprints, because one Sprint has ended and the Issue is now part of a newer Sprint. From your screenshot it appears that only one the first Sprint is pulling through.



Can you please open a ticket with the Smartsheet Support team and we will help look into this with you to confirm if there is a method to pull in multiple Sprints. The Smartsheet Support team can be contacted at the following URL: https://help.smartsheet.com/contact.



Can you please include a copy of the Workflow Execution file, which will help with the investigation. Instructions for gathering Workflow Support Info File:

1. In the JIRA Connector dashboard, select the timestamp under the Last Run column of your workflow. This will bring you to the workflow run history where you can see any error messages for each run.
2. Select the timestamp under Last Run for the latest run of the workflow.
3. On following page, go to the hamburger menu (three horizontal lines in the upper left) and choose Download Workflow Execution Support Info. (Not Account Support Info file)
4. Attach the file to a reply to the contact Support form and we will review as soon as possible.

   Please let me know if you have any questions.

   Kind regards,

   Michael
   
   Smartsheet Support 

Ramzi Khuri

Has there been a resolution to this? My Smartsheet project is pulling in the oldest completed sprint and not the current sprint the issue is in.