Jira User Project Link considerations


Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

 

Summary

When creating a Project Link (to connect Jira to Fisheye or Confluence), does the Project Link need to be created with a user whom will not be deleted or deactivated?  



Environment

All Jira Server/Data Center Environments

Solution

The user that creates the Project Link will be used to access the remote resource (e.g. Fisheye or Confluence).

When setting up project links pick a user that:

  • Has the necessary permissions in both applications.  
    • This will be dependent on what the application link will be used for.  For example, if you are linking a Confluence space to a specific issues inside of a Jira project, the user will need rights to the Jira project (Browse Project, Link and Edit Issues) as well as the permissions to access the desired Confluence space/pages.  
  • Will not be deleted or deactivated.

(warning) The project link will break if the above criteria are not met. 


Last modified on Oct 27, 2022

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.