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.
374 results found
-
Documentation Update - How to create a new View
The Structure 4.5 documentation is lacking when describing how to create new views.
For example, if I take "Basic View" and copy it to my Structure, I would expect that I could edit it, but the View Details screen says
Access: Use - you can use this view but you cannot update it.
There is no "Save As" button as indicated by the documentation.
1 votethanks! please see comments for more information
-
offer a way to save your column widths with a view and with the perspective view.
Our users will customize their view, setting the column widths in a way that allows them to best see the data in the view. While Structure does a great job of preserving this, in their session, there is no way to save the column widths, either in a saved view or in the "perspective view", from the Share button. Our users would like to share these adjusted column widths with other members of their team.
24 votesThank you! please check the comment
-
have a aggregation modifier #fromTopToMe #fromBottomToMe
To provide a backlog forecast it is essential to show what content could be done within a certain time or time budget. If we configure the budget in a top level issues custom field, structure could SUM not only by level, but also the contents of the current list of elements (eg. by priority) and a formula could show from which element the budget is overspent.
3 votes -
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
-
Folder metadata
It would be useful to have folder metadata. There are many uses for this but at a high level you could definitely folder types (strategic vs. operational), provide folder owners etc.
1 votePlease check the comment
-
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
-
prevent double counting
When an issue appears multiple times in a structure (e.g. epic link and issue link),the progress calculation should be configurable to prevent / allow double counting
3 votesplease see the comments
-
Would really like to be able to color fields, columns or rows in structure chart (without having to pay for expensive plugin)
I create some rather large Structure charts with multiple levels of nesting. Want to be able to highlight aspects of the chart (Rows, Cells, Columns) with color. This helps with focus (these items are critical), organization and overall visual appeal.
1 voteThank you for suggestion! It is under review
-
Link a structure to a JIRA board, not just a project
The description of of Structure on the Project page (https://wiki.almworks.com/display/structure/Structure+on+the+Project+Page) is really misleading because this image is of viewing a JIRA board, not a project. With JIRA boards I can use JQL to divide a projects (or multiple projects) issues across many boards, but I do not have a way to link that board to a specific structure that also filters for the same set of issues.
Having a default structure for a project is fine, but I would also like to be able to correlate a structure to a board. This would help teams that for example…
22 votes -
Subscription to a structure view
Jira has a "issue filter subscription" feature, which runs a filter at a certain time of the day and email the user with the results. Structure could have a similar subscription feature tied to a particular structure's view, where a snapshot of that view would be taken at a certain time of the email and the results would be exported to excel and emailed to the user.
My company currently use structure to keep track of our day-to-day progress by manually exporting structures to excel at the same time each day. Automating the exporting would allow us to automate the…
15 votescollecting requirements (see comments)
-
Hide empty folders
In structure folders created based on custom fields will show "no value"-folder in case issues haven't set the related custom field. It would be nice to get an option to define whether to show such "no value" folders or to show such issues without a folder under their parent.
2 votesPlease see the comments for a workaround.
-
Require the user to confirm a deletion of an issue before it is removed from the structure.
Require the user to confirm a deletion of an issue before it is removed from the structure. Right now there is a message that an issue has been deleted, but my users aren't noticing the message. Need to make them verify the deletion before it will occur.
8 votes -
Would like a way to get Structure formula calculations into "normal" Jira custom fields
Structure formulas are extremely useful. Now our users would like ways of using them in other places within Jira. This may be tough in some ways because they are specific to the structure they are part of, but even something simple like the ability to choose an menu option or call some API to commit formulas into an underlying custom field could be quite useful.
4 votescollecting requirements, see comments
-
be able to copy directory path
This feature can help a user orientate an issue in a structure, or share the path with another user easily.
1 votecollecting requirements — see comments
-
Limit the issuetypes for automators so you can use multiple link automators per structure
With Synchronizers it is possible to limit the issuetypes. Therefore it is possible to have multiple link synchronizers for different issuetypes.
Example:
one could defined a parent/child link between epics and features and use a is blocked link between features and bugs. with automators this scenario can not be implemented at the moment.1 vote -
Can Structure use Portfolio Data
Structure would be a great supplement to the information provided by Portfolio. It would be great if this data could be used by Structure ... perhaps even have a Portfolio Structure Template?
7 votescollecting requirements – please see comments
-
Change the colors of the font or/and background of the Structure folders
It would be great to be able to customize the appearance of the Structure Folders in order to have a possibility of manual highlighting the "problematic" folders.
13 votes -
Sync task to add Tasks to Folders
Folders is a great new feature in 3.0 (long awaited) but the sync tasks do not allow tasks to be added to folders which is an obvious feature for auto adding tasks to structure and also a huge use of ordering and sorting tasks in structure.
3 votescollecting requirements – please see comments
-
Progress Bar changes color by ontime or overdue
Allowing users a quick view of the status for more than completion percentage for [insert your object of choice] if they are overdue or nearing completion deadlines
3 votescollecting requirements — see comments
-
Be able to propagate up a risk value
If a sub task had a custom field which indicated it's current risk or similar be able to propagate that up to the top level to show the worst of the risks or some other flag
e.g. if a single subtask of a item is red risk, be able to show that red risk in all of it's parents in the structure. choose the worst value of all sub nodes to show at the parent level.
3 votescollecting requirements — please see comments
- Don't see your idea?