Which of the following is the purpose of transferring ownership of a project?

Cost Tracker project owners might not be able to retain project ownership for a number of reasons, such as their departure from their organization, suspension of their Jira account, or removal from access to Cost Tracker.

Project owners can hand over their projects to other project owners or can have a collaborator make the transfer of ownership on their behalf, if they are no longer available. Since only one owner is allowed per project, the original owner cannot share ownership with the new project owner once a transfer is completed and cannot revert ownership back to themselves. Only a project owner can:

• Change the scope of a project by selecting a different filter.

• Transfer project ownership

• Determines the Jira issues that constitute a project scope based on the filter's visibility

When transferring project ownership, the new owner must have the same permissions to Cost Tracker, to Jira projects and the required JQL filters. For a seamless transfer, it is recommended to perform the Access Permissions Checklist before transferring project ownership.

Important

Accessing Tempo Cost Tracker requires Tempo Cost Tracker Access global permission. Only Jira administrators in your organization are granted access by default.

Access Permissions Checklist

Before starting the transfer, make sure that the required permissions and access to the scope are granted to the new owner. To do so:

• Give Access Permissions to Tempo Cost Tracker

  Grant access to Tempo Cost Tracker in Jira > System > Global Permissions. See more details.

• Share the Jira filter

  In Jira > System click to see if the filter in the project scope is shared under Shared Items and that the filter owner is a valid user. If the owner of the filter is not valid then change it to another active owner or to yourself.

• Verify Jira filter permissions

  Edit the filter permissions for the planned owner. At a minimum the new owner needs a View permission to the Jira filter however, you have the option of granting the View and Edit permissions.

  This is accessed from the Edit permissions > Edit filter in the Jira filter Details page for the filter used in the Cost Tracker project when you click on Scope > View Filter in Jira.

  

• Give access to Jira projects that are queried by the Jira filter inside the Scope

  Make sure to give sufficient Jira permissions to all projects in order for the new owner to view the same number of issues as the current owner. Follow the steps in the Atlassian Support page on how to update project permissions in Jira.

  

  For team-managed and company-managed Jira projects, see managing Project permissions.

Transferring The Cost Tracker Project To A New Owner

When planning to transfer ownership of your Cost Tracker projects to another owner, make sure that the required permissions are granted to the new project owner, as described in the Access Permissions Checklist.

• Only one project owner is allowed per Cost Tracker project.

• Once transferred successfully you are no longer the project owner and you cannot revert the ownership back to you.

• The transfer of ownership is irreversible. In case you want the ownership back, then the new project owner will have to transfer the ownership back to you.

To transfer ownership of a Cost Tracker project:

1. Select a Cost Tracker project and click Configuration in the upper-right corner.

2. Select Sharing in the sidebar under Configuration.

3. Look for the name of the user with whom you want to share the project. The project must be shared with the owner before ownership can be transferred.

   If the name of the user is not listed, then enter the name and click Add. The user is added to the list and the project is shared. The

4. Hover over to the side of the name of the user and click Make project owner to transfer ownership to the selected user.

   

5. Do one of the following:

   • If all the conditions are met as described in Access Permissions Checklist, then confirm and proceed to transfer project ownership.

     The project is transferred to the new owner. You or the previous owner are no longer the owner of this project.

   • If at least one of the conditions is not met, then an error message is displayed with instructions to verify the required missing Jira permissions or missing project visibility, as described in Access Permissions Checklist.

6. If you encountered an error transferring ownership then verify the steps to grant the required access and permissions and try to transfer the project ownership again.

   

   Note

   If the count of issues returned by the filter is different between the current owner and the new owner then a message is displayed. Follow the steps in the Access Permission Checklist √ to rectify it.

7. When all the required permissions and the visibility of issues returned by the filter are the same then the ownership is transferred successfully.

Transferring Ownership On Behalf of a Missing Project Owner

A special consideration is given for project owners who no longer have access to Cost Tracker. Project collaborators are able to transfer ownership from a missing project owner to themselves.

Project owners are unable to transfer the ownership of their projects if they happen to leave their posts or have a revoked access to Cost Tracker, or their account disbaled or removed. In this case a collaborator with the same permissions is allowed to transfer the ownership of a project whose owner is not valid for any of the above-mentioned reasons. To do so:

1. The current project owner must be disabled, removed or has no access to the permission group that grants access to Cost Tracker.

2. As a collaborator, hover over a collaborator to whom you wish to transfer ownership and click Make project owner to transfer ownership to yourself or to them.

3. It is adviseable to change the project's Jira filter and apply it to the project Scope, in case the current filter has restrictions denied to the new project owner. Triggering a Scope Sync on a restricted filter will cause an error.

Important

For any given project there should always be at least one active project collaborator at all times.

If all collaborators and project owners are disabled or have their access removed, then their projects are not visible to be transfered or retrieved by anyone else.

Which of the following is the correct reason the team is released as the last step in the closing?

Which of the following explains why project completion is celebrated?

Who is likely to be the person responsible for implementing the project deliverables?