I suggest Structure should ...

Create sub-issue should work similar to Link New Issue Operation (LNIO)Valiantys

I typically want to create issues of another issuetype, and probably in another project.
Just cloning is too trivial, and it requires to much work to change issuetype, and project.

Alternative (even better): automatically detect sub-issues for certain link-types

13 votes
Sign in
Sign in with: facebook google
Signed in as (Sign out)
You have left! (?) (thinking…)
Jo Wyns shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


Sign in
Sign in with: facebook google
Signed in as (Sign out)
  • AdminIgor Sereda (CEO / Founder, ALM Works) commented  ·   ·  Flag as inappropriate

    Tejas, thanks for your comment. Hopefully, with Structure 1.4 editing an issue is not that painful, as you can do it right on the Structure grid (unless you want it to be in another Project, in which case it's a full Move procedure).

    Note that when you create a new issue, you can also change the initial values of the editable fields - except for Project and Type. The next step for us would be to add Project/Type selectors whenever a new issue is being created in the Structure to make it completely functionally equal to creating a new issue via the standard JIRA screen.

  • Tejas commented  ·   ·  Flag as inappropriate

    We too would like this feature as it would make entering more issues into JIRA very simple. At present it clones the one above and its very painful to edit. our JIRA also sends email on create issue, so the end-user get's an email on the create(clone) and then another when we modify the other values which may change. When you click +Sub-Issue or +Next-Issue maybe a pop-up that would allow a user to clone fields or change before commiting into JIRA/Structure would be really helpful.

  • AdminIgor Sereda (CEO / Founder, ALM Works) commented  ·   ·  Flag as inappropriate

    Jo, thanks for your suggestion. We'll add drop-downs for selecting issue type & project when creating a new issue.

    We will also have additional "total estimate" column, which will display the sum of the estimates - I guess that is what you need for the issue-A.

  • Jo Wyns commented  ·   ·  Flag as inappropriate

    We want to use it as follows:
    Department-A asks Department-B to do something.
    B tells A that it will cost 20 mandays.
    A creates issue in project-A, assigns it to someone from B.
    B can not edit issue-A, but can make sub-issues (internal tasks), which are created in project-B, and estimated.
    Progress on the tasks in project-B should be reflected in the "remainingEstimate" of the issue-A

Feedback and Knowledge Base