Uploaded image for project: 'Jira Service Management Server and Data Center'
  1. Jira Service Management Server and Data Center
  2. JSDSERVER-861

Jira Service Desk should not restrict Project actions



    • 11
    • 19
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.


      NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.

      At current we have an license for all our customers with Jira, however Jira Service Desk is not economical for the highest tier Atlassian customers.

      We have a use case where customers want to:
      1) Edit
      2) Reopen
      3) Initiate
      4) Assign tickets
      for all Service Desk Requests.

      Whilst some people have 'anonymous' customers that do not have access to jira, we already have all our customers as jira-users and pay licenses for this ability (Unlimited). When a Jira Service Desk project is enabled, however, this functionality is removed via the normal Jira Project View and only agents can make these changes. This was not the case for 1.0.

      This means that for non-agent features we need to add all users as agents, even though we do not need/want agent functionality for them.

      To fix this, Jira Service Desk should not restrict to only agents normal jira access to edit, reopen or perform transitions. All jira-users should be assignable owners. Instead, the project permission scheme should be honoured.


        Issue Links



              Unassigned Unassigned
              fc31391d4fda Jacob Briggs
              136 Vote for this issue
              94 Start watching this issue



                Backbone Issue Sync