Skip to content

Anonymous

My feedback

6 results found

  1. 24 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)
    An error occurred while saving the comment
    Anonymous commented  · 

    Waiting for this on Jira Cloud. :)

    An error occurred while saving the comment
    Anonymous commented  · 

    When it will be available for Structure Cloud?

    An error occurred while saving the comment
    Anonymous commented  · 

    Our organization also is waiting for this feature!

  2. 0 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)
    Anonymous shared this idea  · 
  3. 18 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)
    An error occurred while saving the comment
    Anonymous commented  · 

    Hello, David.

    1) in our organization we quite often are moving subtasks (with Jira's "move" feature) from one parent issue to another. Use cases are different. One example: we have user story issue "write a deliverable document to the client" and subtasks are used to break down different paragraphs in the document. And sometimes we see that some of the paragraphs should be written in another document so we move those subtasks to another issue... But this is just one example, we have a lot of use cases. :) So, this feature would be very nice to have in the structure.

    2) We found how to do that. This request is not relevant anymore.

    3) Ability to choose between "original link to be removed, a second link to be created" would be great!

    Anonymous shared this idea  · 
  4. 6 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)
    Anonymous supported this idea  · 
  5. 13 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)
    Anonymous shared this idea  · 
  6. 6 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)

    Actually, that’s something Structure can already help you with!

    Structure allows creating hierarchies using existing relationships between issues in Jira. If there is a link between two issues, Structure can visualize the relationships in the parent-child form, putting one issue above the other.

    You just need to use standard Jira link functionality which is available in any Jira version by default – the ‘blocks’, ‘implements’, etc type of a link. You can configure them at Settings | issues | Issue linking and create links between issues using the Link option on any Issue Page.

    And once links exist between Initiative and Epics, then you can build your structure with the desired hierarchy the following way:

    1. Create a structure.
    2. Click Automation | + | Insert and type a JQL query to match all Initiatives that you want to add.
    3. Then click + | Extend | Linked Items and…

    Anonymous shared this idea  · 

Feedback and Knowledge Base