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
-
Ability to connect to more that one Confluence instance (Structure.Pages)
Current (unless I'm doing something wrong) we can only link one Confluence instance when setting up Structure Pages integration.
It would be nice to have the ability to link more than one. This should come though with the proper UI to select the server when adding a page or searching.
1 vote -
Be able to Receive a notification when an item is manually added to a structure folder and/or it's sub-folders
Be able to Receive a notification when an item is manually added to a structure folder and/or it's sub-folders. That way when someone adds an item or removes one to an existing structure folder, anyone subscribed to notifications for that folder would get an email notification. to implement, just add a button to the button bar when the folder is selected and when you click the button, you get a popup with an option to subscribe to notifications like you do with issues in JIRA.
Obviously, this would only be available for folders WITHOUT automation.
1 vote -
1 vote
Collecting requirements — please see comments.
-
Folders within epics and Epic extension automation
I need to track business Epics, but these are usually large and I like to break them down into smaller-sub-epics to deliver and track (via multiple releases). Jira doesn't support Epics with Epics (unbelievable really) and I need to work at ira as well as structure level so I create folders in structure under the main epic to perform this partitioning. Each Jira story is still linked to the main epic so I can use Epic reporting in main Jira, but it does mean that I can now track sub-epics at the folder level in structure too. Unfortunately this means…
1 voteanalysis — see comments
-
Filter the issues that aren't picked up by the generators
To force a rebuild of the structure based on generator rules only.
The filter would help to identify the issues manually added into the structure.
Then we can decide which issues (all or selected) to remove from the structure if not relevant.Problem: We cannot remove all the issues from the structure. There's a warning when removing at least one issue that is picked up by the generators, and when we acknoledge all the issues come back.
1 votecollecting requirements — see comment
-
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 -
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
-
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
-
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
-
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
-
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
-
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!
-
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!
-
number of comments
Add a count of the number of comments.
1 votethank you for the request!
-
analysis of big data in the structure
Поскольку структура может включать в себя до 10000 задач, будет полезно иметь возможность в отдельном окне проводить анализ этих данных. Какова совокупная трудоемкость в разрезе: проектов, компонентов и т.п. , Какова продолжительность работы одной команды на структуру и т.п. Полезно так же создавать кастомные срезы для анализа типа: стратегические задачи, текущие задачи и т.п.
1 votePlease check the comment!
-
Show additional information on the ressources panel
The ressource panel only indicates the ressource name. For supporting scheduling It would be very helpful to have more information directly in the ressource panel, e.g. "Units", used calendar and a marker or counter that x availability periods are aligned to the respective resource.
1 voteHi!
Thank you for a suggestion. Showing more info is indeed a good idea and it is actually planned.
-
notify if any issues are edited in a structure
Whenever any issues in the structure is edited, notification should go to people subscribed for structure to indicate structure content is changed
1 voteThanks! please check the comment
-
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!
-
Group by Folder
We have a use case where we want this grouping order:
Pre-Code Change (Folder)
Quality Group (Project)
Ticket
Ticket
Ticket Etc
Foundation (Project)
Ticket
Project 3
Obtaining Development System (Folder)
Quality Group (Project)
Ticket
Foundation (Project)
Ticket
Project 3
Coding and Validation (Folder)
Quality Group (Project)
Ticket
Foundation (Project)
Ticket
Project 3
Ticket1 vote -
Add "Basic" search feature as an alternative to JQL
For users who are not well versed in JQL, it would be nice to have the ability to add Jira filters in a way that is comparable to Jira's "Basic" search feature, rather than by inputting the JQL manually.
Perhaps, on the dialog that is displayed when the user adds a JQL insert automation for the first time, we could have a "Basic" link that converts the query to the basic view, just like Jira's issue navigator. Then, all the JQL would be converted into a series of UI inputs (user pickers, drop-downs, etc).
In addition to this, it would…
1 vote
- Don't see your idea?