Presentation on theme: "H OW TO USE M ASTER AND S UBTASKS & H OW TO C OPY AN I SSUE."— Presentation transcript:
H OW TO USE M ASTER AND S UBTASKS & H OW TO C OPY AN I SSUE
We have two scenarios: You have an issue you are working on, and another team needs to do something before you can finish your part, this would be accomplished using Master-Subtasks. You have an issue you have worked on, everything your team needs to do is completed, but another team needs to do something before all is ready for the customer, in this case, you would make a copy of the issue and assign it to the new team, then close the issue for your team.
You have already created your ticket in Footprints, so click on the ‘details’ option to bring it up for creating the Subtasks We’ll start with the Master-Subtask scenario: In this example, a new application that needs to be installed on a virtual server as well as a database that needs to be created for the application on an sql server.
Click the “Subtask” option in the menu at the top of the screen.
Clicking this creates a copy of your issue. This brings up a submenu for creating your subtask.
Click “Save” The correct team gets assigned, Removing the initial team, since they own the Master ticket. Here the brief description gets updated.
You would go thru the same steps to add the second subtask, updating the brief description and assignees.
If your subtasks need to be done in a specific order you can sequence them here. If you go back into your original ticket, you will now see a tab labeled “Related Issues”, you can see the subtasks listed here.
A master will have “+” beside the number. A subtask will have a “-” beside the number. You can see the difference between master and subtasks on the home screen.
You can now continue working on the master issue until complete. Once both of your subtasks are closed, Footprints will send you an email telling you they are completed.
In details view, select “Copy/Move” from the menu list at the top. Scenario #2: You have an issue you have worked on, everything your team needs to do is completed, but another team needs to do something before all is ready for the customer, in this case, you would make a copy of the issue and assign it to the new team, then close the issue for your team. For this example, we’ll use the decommissioning of a desktop computer, the user has left and the machine is no longer needed.
The menu will change, select “Copy in this Workspace”
Update the description. Notice the link to the original issue. You will notice the new issue is open in “Edit” mode.
Remove your team and add the new one. Click “Save” Go to the “Assignees and Notifications” tab.
Go back to your original issue, click “edit” and update the description field.
Update the amount of time spend working on the issue. Then click “Save” to close. Change the Status to “closed” and the Resolution Code to “Completed”
Using these methods, every team gets credit in the metric reporting for the amount of work they do. You will notice even though you closed your issue, the copy is still open and ready to be worked by the next team.
I F YOU HAVE ANY QUESTIONS ABOUT MASTER AND SUBTASKS OR COPYING ISSUES, PLEASE CONTACT SUPPORT. FOOTPRINTS @ MAINE. GOV