Key takeaways
In this module, you learned how to efficiently convert issues or requests into projects or tasks, ensuring consistency and seamless management of project details. You explored the process of selecting conversion options, choosing templates, and managing access and visibility for requesters. By the end of this module, you should now understand how to convert issues or requests while keeping track of their resolution status and planned completion dates.
The following are some of the key takeaways from the module:
- To convert an issue or request into a project, select the issue, use the three-dot menu, and choose a conversion option, preferably using a template.
- Using a template is recommended for consistency and ease, allowing you to review and select the appropriate template based on project requirements.
- The project name and description are copied from the issue by default but can be edited, and custom forms from the issue are carried over to the project.
- You can choose to keep the original issue tied to the project, preventing it from being marked as resolved until the project is completed, or delete the issue upon conversion.
- You can grant access to the project to the requester, and the converted project will be visible in the “converted to” column, indicating whether it was converted to a task or project.
Now it's time to measure how well you learned these lessons with a short quiz.