9.04 - Agile Scrum tables synchronization

This section explains in detail the organization of requirements for table-type synchronizations, whether they are restricted to the active Sprint or not.

Sprints

In Squash TM, sprints are represented as requirement files. Each file is populated with the synchronized requirements that correspond to this sprint's tickets in JIRA. You may filter the tickets arriving in Squash TM thanks to the additional JQL attribute of the synchronization.

Upkeeping the requirements within the sprints

The plug-in will move the requirements among sprint directories if they change sprints in JIRA. If a ticket goes back to the backlog, it will be put back to the root of the target directory.

Backlog

If a requirement is featured in a table but is not currently in a sprint, it will be put to the root of the synchronization target file.

Moving sprint directories

It is possible to move the sprint directories within the same Squash TM project. If moving the sprint directory takes it out of its target directory, the position of the requirements it contains will no longer be updated.

Good habits

Accumulating finished sprints in JIRA will lead to the creation of many sprint directories in Squash TM. In order to improve its legibility, you may want to create one ( or more ) records directory at the root of the target directory and populate it with the finished sprints. It is possible to organize the records directory into sub-directories by year, topic, or any other type of organization that corresponds to your needs.

On another note, if the organization into sprints no longer makes sense, it is possible to move the synchronized requirements anywhere within the same Squash project. The only existing restriction is not to delete older sprint directories. Otherwise, the plug-in will recreate it during the next update.

Also, to enable the plug-in to keep the sprints up to date, it is recommended to neither move unfinished sprints nor their content. This will not cause any error, but you may lose the information that a ticket changed sprints in JIRA.

Once the sprint is finished and the JIRA inquiries are closed, Squash records are free.