Page tree
Skip to end of metadata
Go to start of metadata

This space contains the documentation for the common Atlassian User Management interface, as used in Confluence, JIRA and Stash.

Version of this documentation: User Management 5.0

Note to Readers

Please refer to the JIRA Administrator's Guide, the Confluence Administrator's Guide or the Stash Administrator's Guide instead of the documentation in this space. This documentation is not intended to be read independently of the product documentation in those guides.

Note to Authors

  • All the content in this space is in the form of re-usable chunks, in the inclusions library.
  • The user management UI plugin is versioned independently of the backend libraries. To solve this problem, we will version the documentation space independently of the software. The documentation space will start at version 1.0 (010), and will then move to version 2.0 (020), and so on. We will create a new version of the documentation for any change in either the UI or the backend that impacts the behavior of the software, from the user's perspective.
  • No labels


  1. Confluence is a wiki. You can use it to collaborate on writing and sharing content with your team. Your team can be as small or as big as you like. It could encompass the whole world. Your content can be as simple or as rich as you like. It can be just words, or you can add images, diagrams, activity streams, web service integration and more.

    In a nutshell, a wiki is a piece of software that runs on a server. It publishes web pages that you can read via a web browser such as Mozilla Firefox, Google Chrome or Microsoft Internet Explorer. The thing that makes wiki pages different from other web pages is the edit button. Provided that you have the right permissions, you can edit the page, save your changes, and the updates will be visible to other people immediately..?

  2. Use this parameter to filter the results by label. The macro will display only the pages and other content types which are tagged with the label(s) you specify here. See also the operator parameter.

    You can specify one or more label values, separated by a comma or a space.

    • To exclude content which matches a given label, put a minus sign (-) immediately in front of that label value. For example: If you specify a label value of -badpage you will get only content which is not labelled with 'badpage'.
    • To indicate that the results must match a given label value, put a plus sign (+) immediately in front of that label value. For example: If you specify a label value of +superpage,+goodpage you will get only content which has at least two labels, being 'superpage' and 'goodpage'.
  3. Filters by either the type of contribution made to a page (and optionally its descendant pages), or the watches on the page. Contribution types are:

    • authors - includes people who created or have edited the page(s)
    • comments - includes people who have added comments to the page(s)
    • labels - includes people who have added labels to the page(s)
    • watches - includes people who are watching the page(s).

    You can specify one or more contribution types, separated by commas.

  4. JIRA Service Desk combines the productivity and power of the JIRA platform with an intuitive user experience that allows service teams to focus on the customer. Throughout this tutorial, we will reference the example of a new customer who uses JIRA Service Desk to send requests to his company's IT Team so he can settle into his new role. Here's how the customer and a service desk agent work together to resolve a request using JIRA Service Deskend???

  5. {contributors:limit=10|spaces=ds,@personal|reverse=true|labels=chocolate,cake|showPages=true|noneFoundMessage=Oh dear, no contributors found|showCount=true|contentType=blogposts|include=authors,comments,labels,watches|mode=list|showAnonymous=true|order=update|showLastTime=true|publishDate=2012/06/30}You can also create your own custom reports to query any combination of performance data. Your team members have access to a read-only version of the Reports tab so they can also see the data you're tracking. To create and edit reports, make sure you're logged in as an administrator. ?

    1. Log in as a user with the JIRA Administrators global permission (or the JIRA System Administrators global permission, if you need to remove the JIRA System Administrators global permission).
      (info) By default, the user account created during the JIRA Setup Wizard has both of these global permissions.
    2. Select Administration > Users > Global Permissions to open the Global Permissions page, which shows a list of JIRA's global permissions and which groups currently have these permissions.
      (tick) Keyboard shortcutg + g + start typing global permissions 
      (info) For each global permission in JIRA (indicated on the left of this page), groups which currently have that permission are shown on the right (under the Users / Groups column).
    3. Locate the global permission you want to remove from a group as well as the group you want to remove that permission from (underUsers / Groups) and click the Delete link next to that group.!
  6. {contributors:limit=10|spaces=ds,@personal|reverse=true|scope=descendants|labels=chocolate,cake|showPages=true|noneFoundMessage=Oh dear, no contributors found|showCount=true|contentType=pages|include=authors,comments,labels,watches|mode=list|showAnonymous=true|order=update|page=ds:Advanced Topics|showLastTime=true}

    Separating 'JIRA System Administrators' from 'JIRA Administrators' in default JIRA installations

    By default, the jira-administrators group has both the JIRA Administrators permission and the JIRA System Administratorspermission. Also by default, the user account created during the JIRA Setup Wizard is a member of this jira-administrators group.

    If you need some people to have only the JIRA Administrators permission (and not the JIRA System Administrators permission), you will need to use two separate groups, ?,