Skip to content

I suggest Structure should ...

← Structure for JIRA: Ideas

Deactivate Cut, Copy, Delete

See: https://answers.atlassian.com/questions/12918198/deactivate-cut-copy-delete-in-structure-plugin

The actions should be deactivatable via permission-level or global setting.

1 vote
Vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Jonathan shared this idea  ·   ·  Report…  ·  Admin →
How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • AdminIgor Sereda (CEO / Founder, ALM Works) commented  ·   ·  Report

    Hi Jonathan,

    Thanks for the explanation! But why do you need the users to be able to *add* issues to this structure? Could you limit the permissions to edit this structure to a certain user, who'd be the caretaker of this work package structure? Or do you also have other items besides work packages in the structure too (real issues, perhaps)? In that case, would it work if the permissions were different at different levels in the structure?

    Kind regards,
    Igor

    PS. Did you know that Structure also has API? Since you've already got your own JIRA plugin connecting issues to another system, you can also connect it with Structure and manage structures automatically! https://wiki.almworks.com/x/oYF7

  • Jonathan commented  ·   ·  Report

    Hi igor,

    yes, a fine-grained permission system would be nice. Or a configurable permission system?
    The reason is, we are going to replace our current project management tool with JIRA. the problem is, we cant completely replace our old system. So every issue in JIRA needs to be linked to the old system (link worklog, wirte bills with the existing system, ...; i wrote a JIRA-plugin to manage these tasks). To manage the hierarchy of projects and work packages (both are JIRA-issues with a specific issuetyp) we use structure. And the problem is now, if a user deletes a work package (issue) from the structure or copies one to another, the connection to the old system maybe fails an worklog will be lost. And the summarized hours/ values are also incorrect, if a users deletes an isue from a structure. Thats why it would be nice to deactive these three buttons/ functions. I hope this is understandable?

  • AdminIgor Sereda (CEO / Founder, ALM Works) commented  ·   ·  Report

    Hi Jonathan,

    Thanks for your idea. Repeating from answers.atlassian.com:

    "The reason is, a user should be able to create an issue, but he shouldnt be able to copy, delete oder cut the issue from the structure. Thats why he needs a higher permission than the view-permission.."

    So what you are in fact looking for is a more fine-grained permission system, right? Could you please describe your setup in more detail? Who are these users who are allowed to add issues and why they shouldn't be able to move or remove them afterwards? What are these issues?

    What happens if such user adds an issue accidentally, or places it in an incorrect position?

    Kind regards,
    Igor

Structure for JIRA: Ideas

Categories

Feedback and Knowledge Base

(thinking…)