Skip to content

Martin Wickline

My feedback

1 result found

  1. 86 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Martin Wickline supported this idea  · 
    An error occurred while saving the comment
    Martin Wickline commented  · 

    For our normal issue creation, we have:
    Initiative 1 (Epic 1)
    + Feature 1
    + Story 1
    + Story 2
    + Feature 2
    + Story A
    + Story B
    + Bug C
    And we have issue link types that are different by issue type. For example:
    Feature 1 --(supports initiative)--> Initiative 1
    Feature 2 --(supports initiative)--> Initiative 1
    Story 1 --(supports feature)--> Feature 1
    Story B --(supports feature)--> Feature 2

    We'd like to be able to quickly enter the subordinate issue types, where they auto-link to their parent based on the relevant link type for the parent/child issue types.
    What I'm seeing in current functionality is that all link types for a given structure get applied to any issue that's created, with current synchronizer.
    It leads to incorrect linking of our issue types... not too useful for our purposes.
    If structure could be updated in this way (selective synchronizers?) and sub-issues could be easily created with the child issue type (e.g. first sub-issue of a feature is a story or bug; first sub-issue of an Initiative is a Feature, etc) then we might consider purchasing Structure.

Feedback and Knowledge Base