Support for Atlassian Server Products (and apps like BigPicture) is ending in February 2024.

Are you planning a migration to Cloud? Make sure you don't lose your BigPicture data/configurations in the process. Check out this page for information on how to migrate BigPicture's data to Cloud. If you have any questions please email support@appfire.com

Issue can be assigned only active or future sprints

You can't add issues to Jira sprints that are already closed. 

If you have synchronized your sub-Boxes (such as Iterations) with a Jira sprint field by assigning a task to a sub-Box, you may inadvertently assign a task to a closed sprint. View the use case below to see how this situation may occur. 

Use case

You have a Program-type Box with Iteration sub-Boxes in it. 

image2021-5-24_10-22-15.png

In the OMEGA Program-type Box Configuration, you can see that Iterations (sub-Boxes in the Program-type Box) are synchronized with Jira sprints

Sync works both ways:

  • Assigning a task to a sprint automatically puts it in an appropriate Iteration Box;

  • Assigning a task to an Iteration Box automatically assigns it to a Jira sprint.

So, for example, when you use the Board module to assign tasks to Boxes, even though in the Board module the tasks are shown under Iteration 1, the App will start throwing an error if Iteration 1 is synced with a closed sprint:


In this case, Iteration 1 is synced with a sprint that is already closed in Jira:

  • On the one hand, Jira doesn't let you modify closed sprints (you can't add tasks to them);

  • On the other hand, the App is trying to assign a task to a sprint because of your actions in the Board module.

Closed sub-Box status

Changing the Box status to "Closed" is helpful after the associated sprint has been closed in Jira. The Box color will change to green - the App won't let you assign a task to a closed Box, and the Box status will be easy to see. 

Solutions

You have two ways of addressing the issue:

  • Assign tasks to different sub-Boxes (Iterations synced with sprints that aren't closed)

  • Re-open the sprints → assign tasks to Iterations → close sprints after tasks have been successfully assigned. 

Assign tasks to Boxes synced with sprints that are NOT "closed"

This is the recommended option. If a sprint has been closed in Jira, you probably don't want to associate new tasks with it. Assign tasks to sub-Boxes (such as "Iterations") that are NOT "Closed." 

Also, make sure that the sub-Box status reflects the sprint status. Once you close a Box, the App won't let you assign new tasks. This limits the chances of this error appearing. 

How do I know which tasks should be moved because they don't belong to a closed sprint?

  1. Check which boxes are synced with which sprints.

  2. Check the Sprint Reports of closed sprints. Completed sprint issues that haven't been carried forward to the following sprint are listed on the report. Only those issues should be in a Box associated with a closed sprint. Other issues should not be added to a Box. 

Pick a sprint report to view:

Only those issues should be in a Box synced with this sprint:

Move the tasks accordingly. 

Then, clear the warning log when it appears. 

Re-open sprints

Technically, it is possible to re-open a sprint and make changes if you need to do it. 

To view closed sprints, go to "Reports":

Select "Sprint Report: on the left:

To "Re-open" a sprint, use the button on the right:

Go back to the App → refresh → clear the log 

Now, you can go back to Jira and close the sprint. The error won't appear again.