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.
360 results found
-
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
-
It would be great to be able to clear out the clipboard..
RIght now there does not appear to be a away to remove issues from the clipboard (other than pasting). Seems like a user may try to do a cut / copy and decide they no longer want the issues. Seems like this could be a fairly simple fix (maybe a x button above the clipboard?).
1 vote -
Connnect more than one JIRA instance
When working with external partners they often use their own JIRA instance. You can connect them via the JIRA application link feature with your own JIRA instance and are able to set links between issues in the two JIRA instances this way.
It would be great to be able to display linked issues from the remote JIRA in your own structures.
2 votesCollecting requirements – please see comments.
-
Allow re-formatting aggregated time fields (e.g. into hours).
We are budgeting a project - so we need to show a rollup of hours and then an extension of these hours into costs.
So we need to be able to:
a) format time so that it doesn't simplify 60 hours spread over in a year into 1w 2d 4h - it needs to show as "60 hours"
b) provide a column that does math on the 60 hours. e.g. 60 hours at $125/hr = $7500Together we will rid organisational planning of excel :)
M.
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 -
support grouping of issues by link type
e.g. all 'Blocked By' issues added via Extend automator grouped together under parent.
This makes the Jira relationship between Structure parent/child issues clearer.
3 votes -
improve "templates" functionality and provide simple interface to work with it
- That's will be useful to have a possibility to create structure by one click. Ex. It could be a quick button (as jira has "+ Create issue" at the right top conner). When I click on it, I can choose template name & click create. That's all.
- Sub-tickets in template structure should be predefined, so I don't want to specify each time what project it should be and what options to copy.
- In existing structure that's will be nice to have a possibility to create tickets\sub-tickets using templates for issue. Ex. I want to have a possibility to easy create…
13 votes -
Creating structures from agile boards with Epics and Epic-less tickets
When creating a structure from an Agile board it would be nice to be able to add as well Epic as stories not assigned to an Epic.
Creating a structure with Epics and adding an JQL-Inserter for the Epic-less Stories is not sufficient. I am not able to move Stories into an Epic later on the structure board this way. ("Cannot remove issues from JQL query result. ")
3 votesplease see the comment for an alternative setup
-
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 -
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 -
Allow to see the structure in the issue type 'Test'
When viewing an issue of type “Test”, created by Zephyr and assigned to a Structure, we are not able to see the corresponding Structure section as expected. If we change the type of the issue to anything else (Bug, Story, Epic, etc.) then the Structure section becomes visible. It seems that either Structure or Zephyr is not playing well together. This is critical to our organization as we try to integrate structured testing into our organization.
3 votes -
Reinstate search on the issue page
In Structure 3, search and filtering functionality was removed from the issue page. But sometimes we need that to rearrange structure without leaving a specific issue.
More feedback:
But with the loss of the toolbar we can no longer filter or search the structure from the issue view.
We frequently need to unpin, search then re-org the structure, and we like to do it from the issue view. At my work we are considering rolling back to 2.x to get the search/filter feature back on the issue view.
7 votes -
Structure lite
Have you ever thought about a lite version of structure with reduced functionality? e.g. only supporting parent / subtask or epic / story relations or homogenous link hierarchies for example.
1 vote -
Show progress of selected issue/task in Confluence
In our company we use very closely JIRA and Confluence. Structure allows us to properly organize issues based on our demands and workflows and it works perfectly for people who are assigning tasks or implementing them. But we use Confluence for executive summary of progress on specific builds where would be very helpful if we can display progress bar of a specific issue (counted from all issues below of selected issue in the hierarchy). This way we would be able to create great overviews like e.g. "Bug fixing of Feature1", "Implementing Feature2", ... with progress bars behind without a need…
2 votes -
Name in issue viewer
When beeing displayed in the issue viewer and the default structure name should be "None" to avoid confusion as another structure name makes it seem to belong to one.
3 votes -
Allow you to wrap text in a column in the structure view.
I would like to be able to see 6 columns and have the option to see ALL the text wrapped not just the starting text. I'd like to retain the option to just see the starting text too though. I have used the full screen real estate but I can still only see the start of the wording.
Current work around is to only have 1 or 2 columns showing at once and add in the others as necessary later.
e.g. View currently shows:
Summary Description Labels Components Assignee
Client Doc Data in clie Docum Disclosure Sarah Sm
I'd like…
107 votesat least partial solution shipped with Structure 4.2, see comments
-
Show sum of time columns
I would like the bottom line of the structure widget to also show the sum of remaining estimates for all (shown) issues in the structure.
For example, I have a structure with issues for our next release. I would like to enter a filter like "fixVersion=<currentSprint>" to see issues assigned to the current sprint, how they are spread across overall plan, and also see the remaining estimates for the sprint.
The bottom already say something like "Showing 25 issues (100 issues are not shown)", so there's quite enough space to say "Showing 25 issues (10 weeks remaining) | 100 issues…
24 votes -
Integration on Jira Agile
It's very useful the integration with Jira Agile (on Jira 6 and next releases), so I can see near the tab Epic and Version (in the backlog view) also the other structure that I can build.
Actually, I have to manage two different views: Structure view and Backlog view. It's better to integrate this two views.1 voteplease see comments
-
Auto-Convert Perspective-Link into Structure-Gadget on Confluence-Pages
In this way one is able to create whatever view of the Structure in the structure itself and share this on Confluence pages without dealing with the UI of the gadget (which needs some improvements).
1 vote
- Don't see your idea?