Walter

← Customer Feedback for Structure Plugin for JIRA

My feedback

  1. Possibility to disable/filter the Structure notifications in the project & user Activity Streams

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Structure for JIRA: Ideas  ·  Flag idea as inappropriate…  ·  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
    Walter shared this idea  · 

  2. Limit visibility of structure on an issue

    8 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    under review  ·  3 comments  ·  Structure for JIRA: Ideas  ·  Flag idea as inappropriate…  ·  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
    An error occurred while saving the comment
    Walter commented  · 

    2 - 3 : Indeed configuration per structure level (on Edit Structure) : *this* structure is available to <list of types>.

    4 : Only nice to have : but if cookie implementation remains in the future then you could add logic that changes cookie info for
    * changing the order of the structures in the "select" box
    * to indicate this is the default structure for the current issue type
    * to indicate this is the default filter for the current structure
    But only nice to have.

    Walter shared this idea  · 
    An error occurred while saving the comment
    Walter commented  · 

    1. When no structure is available for the user (e.g. no view rights are defined for his role) => do not show the 'structure section' (as this can be confusing). This the follows the same logic as subtasks/links where the sections are not visible if no subtasks/links are available.

    2. Define for which issuetype the structure is available/not available.
    As you can now create multiple structures (which is great btw!) you can start linking structures to certain issue types

    3. Define which issuetypes shows the 'structure' section and which don't.
    (can be implemented by the combining the above 2 features)

    4. Define the default structure for an issue (when multiple structures can be consulted)

  3. Propagate field values down the hierarchy

    65 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    accepted  ·  12 comments  ·  Structure for JIRA: Ideas  ·  Flag idea as inappropriate…  ·  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
    An error occurred while saving the comment
    Walter commented  · 

    Indeed.
    More or less the same functionality as exists in the LNIO plugin. See image https://plugins.atlassian.com/server/1.0/screenshot/fetch/11746 (in french)
    thx

    An error occurred while saving the comment
    Walter commented  · 

    Needs this also.
    Basic implementation : a list of fields for which the data needs to be copied to the new child issue.
    Extended implemenation : a mapping table - "from parent issue field to child issue field"

  4. Limit parent-child relationship to specific types of issues

    86 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    accepted  ·  20 comments  ·  Structure for JIRA: Ideas  ·  Flag idea as inappropriate…  ·  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
    Walter supported this idea  · 
    An error occurred while saving the comment
    Walter commented  · 

    And need this also. Currently we tell the users that the type of the first child issue needs to be changed, from then on he can create sibling issues and the type is copied. It works but UX drops.

Feedback and Knowledge Base

(thinking…)