Structure for JIRA: Ideas
Thank you for visiting our feedback website! Feel free to vote or post your own ideas. Make sure you turn on the option to notify you about changes and comments in your account settings, so that you can stay updated about the progress of the ideas you’re interested in.
384 results found
-
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 votesplanned after 1.0
-
Use different fonts for the levels in the hierarchy to make them more distinct
It would be great for easier differentiation to make the font larger for higher level issues in the hierarchy. E.g.
Level 0 - H1 Bold
Level 1 - H2 ...
Level 3 - H3
etc12 votes -
Group by Formula
Have issues in your hierarchy grouped by a specific formula using a new generator.
12 votes -
Open structure issues in Issue Navigator
Similar to functionality in Greenhopper and other plugins, add a button to structure to allow opening the list of issues visible in the structure in the Issue Navigator.
I use the Agile Cards plugin. It's possible to print cards from the Issue Navigator. I would like to be able to print cards for a portion of the hierarchy in a Structure but I have no way to get from the structure to that functionality. One possibility is to allow opening the issues currently visible in the Structure in the Issue Navigator.
It seems like this would be useful for other…
12 votes -
Allow an attachments column with attachments preview, similar to the Images column
The structure view should allow the user to display "attachments" as a column, where attachments are listed similarly to the "Images" column. Clicking on an attachment thumbnail would popup a preview of the attachment.
At the very least it should allow the user to download the file without opening the ticket itself.
12 votes -
Have some kind of integration with zephyr to manage test cases
I would like to see which test are passed and failed. It would also be nice to see the defects or bugs in the structure and create my test cycles with a structure.
12 votes -
Need additional mark for Closed issues
Structure shows check mark when issue is resolved, but I want another mark if issue is closed!
11 votes -
Allow referencing a formula based Structure column within S-JQL expression
Currently, I can only refer real fields of a JIRA issue within S-JQL function structureQuery parameter.
Example: "issue in structure("Planned Stories", "issueOrAncestor in [type = Epic and status = Open]")"
But it will be absurdly powerful if I could refer to a formula based Structure column values, existing in a selected View in e.g. such way:
issue in structure("Planned Stories Structure","Planned Stories View", "issueOrAncestor in [type = Epic and 'Adjusted Storypoints' > 'Planned StoryPoints']")
11 votes -
Export to Google Sheets
Make it possible to directly export a structure into Google Sheets. It will save one step converting an Excel file into Google Sheets.
10 votes -
Please add Expr function to return number of working days between 2 dates or in general work with Calendars defined in Gantt
Hi Almworks,
We need very simple capacity management in Structure. For this to work we have almost everything:
- ability to aggregate from tasks to Epics (and higher levels) for remaining estimates and spent
- Top-level group can act as a teams, for which we can defined daily capacity and planned work ratio (using field with CASE() for example)What we lack is we can't calculate remaining capacity considering resources availability, mostly because we can't use production calendars (similar to NETWORKDAYS() of Excel) If we had this ability we could automatically build Structure view which shows current remaining estimates vs.…
10 votesCheck the comment please, thank you!
-
Strikethrough on closed or resolved issue
A closed or resolved issue should have have a "strikethrough" on the summary.
10 votesPossible as per-user CSS customization feature
-
Support 3+ Multi-Cascading Selects
Automation + Grouping on Multi-Cascading Select fields is a top-notch function that allows users to efficiently organize complex datasets, but are functionally limited to deeper organizations.
If I start using the Jira-system 2-tiered multi-cascading select field in Structure for my issues, but then decide I need to switch to a 3-tiered mutli-cascading select to model my data, I sacrifice the functionality of Structure for the flexibility of another add-on.
Including support in Structure for n+ Multi-Cascading Selects, e.g iDalko's multi-select field (using MySQL), would help users like myself fully harness the capabilities of automated issue structures
9 votesissue in backlog, update will follow when delivered
-
notes
To fully take advantage of the new Notes field it would be really nice to make it independent of the issues to which it is added. As it works now, if a structure contains a multiple of the same issue and a note is added this note is attached to all of these issues.
Separating this is actually the only thing left to be able to use the structure plugin as a product structure documenting an entire product portfolio. One issue for each part and the notes field (renamed "Qty" or similar) to hold the amount of parts of the…
9 votesThank you! Please see the comment
-
Structure Filter improvement: project without structure enable need a hint from the plugin
When use a JQL with project field and the project have no flag to support structure show a hint warning the user that needs to enable the support to structure, or will be excellent to choose to enable it.
The current implementation only shows no search results.
The uses get confused and don't know if the plugin is working or they are doing some misconfiguration.9 votes -
Pin more than one item
A very important and urgent request:
Is it possible to select multiple issues with the pin?Or is there any other possibility to choose more than one issue, as the filters dont allow the "OR" request
9 votes -
Quick Grouping and Sorting
Currently we can only use quick filters. The most used feature in our customer projects (datacenter) is the quick group feature.
This feature should be available on structure cloud as well, because it makes the use of structures so much more flexible and enhances the usability.
Currently our users create a lot of new structures just because of this missing feature. Obviously this leads to maintenance issues, because all other configurations need to applied across multiple structures...Same goes for Quick Sorting, but the grouping option is more important.
9 votesHi Martin,
With the latest update, we've added quick grouping capabilities. Sorting by a column is already available for our users. Please, take a look and let us know if it solves your use case.
Quick groups:
https://wiki.almworks.com/documentation/structure/9.0/cloud/quick-groups-187662723.html
Sorting by columns:
https://wiki.almworks.com/documentation/structure/9.0/cloud/sorting-by-columns-157319184.html
-
I should be able to create a "Structure Template" and choose while creating a new structure
I want to create a structure. When I go from the menu, it shows me a "Select Template" pop window, where it shows me below templates.
1. Empty Structure
2. Backlog Structure
3. Agile Structure
4. Gantt Chart
5. Agile Gantt ChartI want to create a customized template so that whole of my organization product groups use the same, instead of re-inventing in their own way. This will help my organization to build a standardize look and feel of structure and create ease of navigation.
Please do let me know, it there is already s solution to it. Else…
9 votes -
expose a structure's "order" so JQL queries and filters can be created to list issues in that order.
The order's created would be very handy to be able to query in JQL - something like: project = MARSCOLONY AND assignee = "cosmonaut" ORDER BY "taskorder1-structure" ASC
This would allow exposing structures in Confluence and other places in a useful way.
Not sure what to do about different levels, but initially just ignore issues that aren't at the top level?
9 votes -
Have option to show multiple tasks on one row in Gantt
Currently we are using a different app for this but would prefer to use Structure.
9 votesHi Peter,
Thank you for the suggestion, we’re evaluating this idea and figuring out how to do it the way it will work for most use cases. Can you please describe your use case in more detail?
Thank you!
Regards, Alexey
-
Group by Link Type
Group by Link Type.
We have many link types used to represent different things.
E.g.
- A "Story" ticket may [LinkType: Satisfy] many "Acceptance Criteria" tickets
- A "Bug" ticket may [LinkType: Block] a "Story Ticket"
- An "Epic" may [LinkType: Solve] a "High Level Requirement" ticketWhere tickets have multiple types of link coming from them, would be nice to have that as an explicit folder / grouping in the tree.
E.g.
Story XBlocked By
Bug Y
Bug Z
Solves
Acceptance Criteria A
Acceptance Criteria B9 votes
- Don't see your idea?