Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-20234

A new sharing permission for "editing" filters and dashboards should be created

XMLWordPrintable

    • We collect Jira 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 Server. Using JIRA Cloud? See the corresponding suggestion.

      When JIRA 3.13 was released we added "shared dashboards and filters". And while that was a step forward, it seems now we need an extra "share permission" that of "editable by others".

      The use case is that some one in a team can create (and hence own) the shared dashboard or filter, but others in the team can "edit/improve" the situation by being able to edit the dashboard/filter. This promotes better team integration.

      In terms of code change, this is very doable. Currently the dashboard service and search request service check for ownership when deciding if the person can edit a dashboard/filter. It could check also for this new "edit permission" and retain the same interface otherwise.

            [JRASERVER-20234] A new sharing permission for "editing" filters and dashboards should be created

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3058637 ] New: JAC Suggestion Workflow 3 [ 3693776 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Component/s New: Dashboard & Gadgets [ 43416 ]
            Component/s Original: Dashboards & Reports - Manage Dashboard [ 43409 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2603251 ] New: JAC Suggestion Workflow [ 3058637 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2552360 ] New: Confluence Workflow - Public Facing v4 [ 2603251 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2340289 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2552360 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 2109637 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2340289 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2074104 ] New: JIRA Bug Workflow w Kanban v6 [ 2109637 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 889096 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2074104 ]
            jonah (Inactive) made changes -
            Description Original: When JIRA 3.13 was released we added "shared dashboards and filters". And while that was a step forward, it seems now we need an extra "share permission" that of "editable by others".

            The use case is that some one in a team can create (and hence own) the shared dashboard or filter, but others in the team can "edit/improve" the situation by being able to edit the dashboard/filter. This promotes better team integration.

            In terms of code change, this is very doable. Currently the dashboard service and search request service check for ownership when deciding if the person can edit a dashboard/filter. It could check also for this new "edit permission" and retain the same interface otherwise.             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-20234].
              {panel}

            When JIRA 3.13 was released we added "shared dashboards and filters". And while that was a step forward, it seems now we need an extra "share permission" that of "editable by others".

            The use case is that some one in a team can create (and hence own) the shared dashboard or filter, but others in the team can "edit/improve" the situation by being able to edit the dashboard/filter. This promotes better team integration.

            In terms of code change, this is very doable. Currently the dashboard service and search request service check for ownership when deciding if the person can edit a dashboard/filter. It could check also for this new "edit permission" and retain the same interface otherwise.
            jonah (Inactive) made changes -
            Link New: This issue relates to JRACLOUD-20234 [ JRACLOUD-20234 ]

              Unassigned Unassigned
              bbaker ɹǝʞɐq pɐɹq
              Votes:
              65 Vote for this issue
              Watchers:
              35 Start watching this issue

                Created:
                Updated:
                Resolved: