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.
98 results found
-
Granular control over Automation grouping, particularly with Labels
Currently, grouping within Automation is kind of an "all or nothing" approach. For example, we use labels to identify which "product" our epics are for, but we also use the Labels field to track other information. For our main Structure, what we want to do is have the Automation grouping only look at the 6 labels we currently use for "product" tracking and ignore all of the others, but I cannot seem to find a way to do this without manually creating my own folders and setting up the Automation for each one; the drawback to this is we can't…
5 votesThank you!
Check the comment, please.Julia.
-
Have option to customize or hide what buttons are shown
Trying to get users to update information who are less familiar with Jira. Want to customize what options/buttons users see so it's less overwhelming.
5 votesthanks! please check the comment
-
Add Project Category
Structure recently added the ability to use "Status Category" as a column. As Categories can be pretty powerful tools, I would like to suggest bringing "Project Category" in as a column as well.
In addition to columns, the bigger need I have at the moment is to be able to "Group by" Project Category in the Automation options. I also noticed that Status Category is missing here as well, so I think it would be great to bring the existing work to the Automation section as well.
4 votesThanks! Please check the comment
-
Use the standard Atlassian User Interface objects
I would suggest you to resort exclusively to the AUI objects for your interface instead of your custom ones that clearly gives the impression that you are exiting the Jira world to step into another one.
I think you user would deserve a smoother user experience, with the same kind of buttons, icons, tables to which they are already used to. I'm especially talking about the transformation/filters features that should be improved in that direction to my mind. Thanks for you great achievement!4 votesplease see the comment
-
Structure of Structures - no data just an index with link to the relevant structure
I would like to create a Structure of Structures for structure navigation, whereby specific child elements allow you open the referenced structure. I have many structures that contain the same data, just displayed differently for different user groups.
The use case is in essence:
Parent - Folder (a name listing a group of similar or related structures)
Child - New Structure Link - simply a mechanism to either open or navigate to the referenced structure - includes description.Implementation:
Is it possible to add a new Structure element into the "Add" Dropdown called "New Structure Link". (i.e. New Issue, New…4 votesThank you!
Check the comment, please -
Enable group by Elements Connect (formerly nFeed) fields
Enable nfeed field for the Group by function
plugin link: https://marketplace.atlassian.com/apps/23337/elements-connect-formerly-nfeed
4 votesThank you for the request! Added to backlog
-
Add a vertical option for "Grid + Details" Layout
Currently when using the "Grid + Details" view it only provides the ability to view the issue details in a panel to the right side of the structure view.
Many engineers however tend to use their screens in vertical mode and thus this side-by-side view is less than ideal as it gets cramped fast.
For these users, it would be really nice to have another option for "Grid + Details" layout where the issue details panel appears below the structure hierarchy panel rather than to the right.
4 votes -
Add activatedDate property to Sprint item in Formulas
Jira Structure Formulas currently provide following Date type properties within Sprint item: startDate, endDate and completeDate:
When I compare it with official Jira REST API, it seems that there is missing activatedDate property:
https://docs.atlassian.com/jira-software/REST/9.5.0/#agile/1.0/board/{boardId}/sprint-getAllSprints
Would it be possible to extend Sprint item object with activatedDate property, so that it’s possible to access this value via Formulas column using Expr language?
Usecase is to create Structure which shows same level of information as original Jira Sprint Report page, however currently it's not possible to mark issues which were added to the sprint after it's start (activation), because of missing access…
4 votes -
Color quick transformation buttons to allow faster identification and categories
Currently, when you add a quick transformation the buttons are all white/clear. When you have a large number, it can be hard to find the transformation your looking for.
With colors, you could create visual categories (i.e. groupings, component filters, label filters, etc) and the user can navigate to them much faster.
4 votesThank you!
-
Use Monaco editor for editing formulas
The Formula column is a killer feature, but it can get tricky when the formula expression grows larger than the size of the editing area, and has a few levels of nested expressions.
Beyond just the ability to enlarge the editor, it would be fantastic to have a more advanced editor to assist here, and the obvious candidate is the https://microsoft.github.io/monaco-editor/
My suggestion for iterations for this would be:
- Just replacing the actual editor and make sure it's still working when editing and not (so no functional changes)
- Adding config and definitions needed for highlighting brackets and auto…4 votesThank you for request!
-
Risk Management in Structure
For our company would be useful a risk management addition, a same feature as Big Picture has with the Risk matrix.
4 votesThank you for the suggestion! check the comment, please.
-
Automated Export of Formula-Based JIRA Structure Reports
I propose the introduction of a feature that enables users to automatically export JIRA structure reports, particularly those built using formulas. The export functionality can be facilitated through a REST API or a scheduler, with outputs in the CSV format for example.
My need for this feature arose when I attempted to retrieve the report via the existing API, only to realize that the current system doesn't support this (I can only get list of standart attributes). A review of the documentation confirmed the absence of such a feature.
Thank you for considering this suggestion.
4 votes -
integrage Jira Asset Management Fields
I propose integrating Jira Asset Management with Structure to elevate the management of asset-related data. Ideally, this integration would enable the grouping of Asset Fields, simplifying the display of these fields in dedicated columns within Structure for enhanced organization.
4 votes -
Option to change font style of Summary text for different levels of hierarchy
Formula column with Wikimarkup is great, but since you cannot use this on the Summary column (which must be included in the Structure as is) there isn't a way to clearly distinguish the different levels of your hierarchy. Would be great if you could opt to bold the Summary column for Level 0, for example.
3 votesThank you for your request! Please check the comment
-
"Sum over Sub-items" For Dates / Aggregate Dates - with the ability to choose Max or Min Date
I'd like to see my dates roll up the hierarchy so that I can see higher level estimates as they roll up. For example, if I have a folder for a project and I have a number of tasks underneath, I'd like to see the latest due date in the project, or the earliest start date.
3 votesAlready possible with latest Structure – see comments for details. More improvements are coming.
-
Set different views for folders
Different folders in Structure may have different needs for columns/views, so it would be great to be able to define a view to use for each folder.
3 votes -
Integrate with zephyr for Jira
Integrate with zephyr for Jira to be able to get the test execution and the linked defect related information into structures. Currently structures is able to show the Zephyr test case , but not the test execution status and the linked defects
3 votes -
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 save and "Perspectives" or combined set of Structure, View, Enabled Quickfilters that you can save and share
Users get overwhelmed with the number of options that they have to change the way they visualize the data in the structure.
Currently we can share a perspective which is similar functionality to what is being requested. However we cannot keep a library of perspectives in the system the same way we have the Views. This would help provide users with a library of options based on what they intend to do (i.e. risk management, project prioritization, reporting, etc.)
3 votes -
Show keyboard shortcuts more prominently
The keyboard shortcuts looks great, however discoverability could be better. Even technically minded individuals in the majority do not go searching for keyboard shortcuts.
Adoption of Structure may be more natural and frictionless if users were shown a permanent reference to keyboard shortcuts.
3 votes
- Don't see your idea?