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
-
allow showing worklogs for a specific sprint and team
I assume a lot of people want to use structure for reporting as well. Most teams work with sprints and therefore it is essential to be able to select "sprints" as a filter for worklogs in structure views. A structure/or view could show worklogs for a certain sprint only and besides also for the involved team as well
6 votesThank you for idea! please check the comment
-
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)
-
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 -
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
-
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
-
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 -
Add progress aggregation based on the number of sub-items
Parent issue progress % seems incorrect based on underlying children progress % values, assuming equal weighting per child.
Example screenshot: imgur.com/a/43lgW
6 votes -
Not override the functionality of the JIRA Create button
I think the decision to override JIRA's big, blue Create button in the top navigation is a mistake. And it's causing some headaches on our end. We have non-technical users who are using the Structure (with edit permissions) who aren't aware that creating a new issue will add it to the Structure they're viewing. They simply want to create an issue, not necessarily add it to their structure. We could remove the button easily, but then we'd have to have our users jump to another JIRA screen to create an issue. That's design breakage! My opinion is, leave the ubiquitous…
1 voteReviewing options – please see comments
-
Report or filter on accumulated fields
FIelds like 'progress', 'estimate' or 'logged' are calculated (accumulated) over the sub-structure under the issue. I would like to be able to report those values in reports (e.g. accumulated estimate) or use them in JQL queries (e.g. accumulated_estimate > 2w)
5 votesCollecting requirements, please see comments.
-
Print Structure Cleanly
Right now, I have two choices, export to Excel or print from the structure board.
In our situation, the description and acceptance criteria have bullets, numbers and other items allowed in JIRA's rich editor.
When exporting to Excel, this renders as HTML tags which Office does not accept and render correctly.
When using the print functionality, JIRA Issues cross over page breaks (which we could fix if we could have it render in Excel)The reason this is a concern for us is that or customers want to be able to review the technical architecture. ePrinting is our only real…
2 votes -
Structure subscription
I have been searching for an option to subscribe to a structure (similar to a filter). If this is not available, it might be a good idea to add this as some of the structures cannot be created using filters.
1 voteplease check the comment!
-
Yellow "x items selected" box shouldn't push list of tickets down when it appears
Hi! I am using version 4.6.5
When you select a ticket, the yellow "x items selected" box appears, and visually pushes the entire ticket list down so you visually "lose" the item you just clicked on.
To see the problem in action, scroll to the very bottom and select the circle for the very last ticket. Instantly, the ticket gets pushed downward and disappears, so you have to scroll down to see it again.
It's also a problem when I have some tickets selected, then do ctrl-A, ctrl-A to deselect all tickets. The yellow bar that was there goes away,…
3 votes -
Hide the days and unworkable hours of the gantt grid. Especially when it is extended to the maximum (hours)
When the maximum detailing of the gantt chart is done, the days and hours that do not end up representing a greater amount of columns in the gantt. It would be much more practical with great visualization without these columns. Especially when there is a need to visualize tasks that are defined with small loads of hours and to be executed on the same day.
1 voteHi Milson!
Thank you for your answers!
-
analysis of big data in the structure
Поскольку структура может включать в себя до 10000 задач, будет полезно иметь возможность в отдельном окне проводить анализ этих данных. Какова совокупная трудоемкость в разрезе: проектов, компонентов и т.п. , Какова продолжительность работы одной команды на структуру и т.п. Полезно так же создавать кастомные срезы для анализа типа: стратегические задачи, текущие задачи и т.п.
1 votePlease check the comment!
-
Allow importing XRay tests creating a tree of folders corresponding to a test path in the XRay test repository
XRay instroduced a Test Repository in v3. Now every XRay test has a field 'Repository Path' looking like: '/Test Repository/Release 1/Phase 1/AAA/'.
However, the Structure view is still better than XRay repository. It would be great to be able to import XRay tests recreating the same folder structure as in the XRay test repository automatically. So that users can use both XRay test repository AND Structure.
3 votesThank you! please check tthe comment
-
Ability to hide the time line in the gantt chart view
It is a widely adopted practice to not share specific dates in long term planning and it would therefore be helpful if I could hide the dates/timeline in the gantt view.
The only option today is to zoom out but that is not practical as the feature-bars will become to small and the timeline is still visible but in years.
I want to be able to show how feature A is scheduled before Feature B and that it is dependent upon Feature C being completed without having to show when the features will be worked upon.
Simply hiding, or making…
3 votes -
add hash marks to the parent bar in Gantt based on child dates
Allow the ability to add hash marks to the parent time bar in Gantt based on child dates. This would allow to see milestones without cluttering the view with multiple child issues.
1 voteHi Jamie!
Thank you for a suggestion and a feedback!
-
Have the ability to extend with certain add-on provided entities such as Adaptavist Test Management for Jira (kanoah).
I know it's not likely that you can interface with every other add-on that structure customers might also use, but selfishly, I would love to be able to view all test cases associated with an issue under that issue (similar to Extend with linked issue).
1 voteThank you for suggestion! please check the comment
-
Choose what group label to display and which order for field fixVersion
This idea is a to provide a way to display only (or to hide) some fixVersion instead off all of them when we use the grouping feature. If it is possible to choose the storing order (asc, dsc) it would be awesome !
3 votesthank you! check the comment, please
- Don't see your idea?