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.
158 results found
-
Bulk edit for selected items
Structure Cloud should have the option to bulk change selected items in the structures or at least open the selected items in the Issue navigator.
This would be a massive time-saver!
7 votesHi Martin,
Thank you for reaching out!
I'm happy to let you know that now you can bulk edit up to a couple hundred items at a time.
You can learn more about our latest update here: https://structure-cloud.releasenotes.io/release/L10Ds-text-wrapping-and-quick-grouping-are-coming-to-structure-cloud
-
Be GDPR Compliant
I need Structure Cloud to be GDPR compliant. I use structure heavily, but my company will stop using structure because it is not GDPR compliant.
3 votesThank you for your request.
Structure for Jira Cloud is GDPR compliant. Structure does not collect, store or process Personal Identifiable Information.
We’re updating our documents related to Security and Privacy. For now, you could read our Security and Privacy FAQ to learn more about how we work with data.
https://wiki.almworks.com/documentation/strcloud/structure-cloud-security-and-privacy-faq-69307370.htmlCould you please share a little bit more details about what makes you think that Structure is not GDPR compliant?
-
Present a warning or confirmation dialog box prior to removing a generator from a structure
There is no undo for accidental deletion of generators or folders.
If you accidentally delete a root folder - you can lose everything!3 votesThe feature has been implemented! Now you can undo the last operation in the structure if an element was moved or removed.
-
Allow formula as option in grouping structure in Automation. Group Automations currently support grouping the issues by custom Jira fields
Under Automations, issues can be group only by custom field. It will be better if Jira Structure can support grouping by using formulas. Ex. I can instead group issues by month it was created, just by calculating the month from created date.
6 votesI will change the status to “completed” since it is done already but feel free to contact us.
Thanks! -
Expr Language Documentation Shows Semi-Colons in Formulas, but You Can Use Commas
All the Expr language documentation shows semi-colons in formulas, but you can use commas. It would be good to indicate this somewhere as many people are in the habit of writing commas inside formulas to separate arguments and it is hard to get into the habit of typing semi-colons just when using a structure formula.
1 voteThanks! please check the comment
-
JIRA Dashboard gadget for cloud
JIRA dashboard gadget would be good showing a pre-defined structure.
7 votesThe feature has been implemented. Structure data can now be displayed on the Jira dashboard, alongside other reports.
-
Resource leveling by rank, to respect the backlog order
According to Scrum the backlog order/rank defines the priority of an issue. When applying resource leveling, there is no option to respect this priority by placing first issue, delaying the next and so on.
6 votesStarting from Structure.Gantt 2.4 it is now possible to use Rank as Resource Leveling priority, see Release Notes for more details: https://wiki.almworks.com/x/RIBKBQ
-
Option to hide automation rules
I would like to be able to toggle automation rules from appearing in my Structure. Some Structures have only a few issues (for example, a hotfix release) but many rules because I have a standard set of rules for release Structures that include top-level issues, and links to blockers, duplicates, tests, and requirements.
Additionally, users who cannot edit the Structure generally do not need to view the rules, so they should be able to toggle them off.
6 votesThis suggestion has been implemented. It is now possible to hide or show automation rules by toggling on or off the Automation button.
-
Structure.Gantt for the cloud?
Are you working on developing the Structure.Gantt addition to be used on the cloud version?
12 votesHi there, Structure.Gantt for Cloud is available for some time already, we’re working hard to bring all of the On-Prem features to Cloud, please give it a try!
-
Export to Excel from Structure for Cloud
Allow for the exporting of Structures to Excel from Structure for Cloud
32 votesI’m pleased to inform you that Structure Cloud now supports export to Excel.
You can also subscribe to our Structure Cloud release notes and get updates on all new features: https://structure-cloud.releasenotes.io/ -
Folder Item Count
I would like to see the number of items I have in a folder without having to manually count them each time. For example, if my folder was named 'Bugs', then maybe it would display as
Bugs (9)
3 votesThanks! Please check the comment
-
Allow modification of Jira issues order/links in directly in Structure for Cloud
Currently when using automation to bring in issues and show the linked status they is no ability to update order or the link between other issues. Ideally issues could be reordered to identify priority or possibly even have their links modified when dragged to other hierarchies (similar to the status being changes when dragged on a KanBan Board)
21 votesBoth requested features have been implemented! Now you can change Jira issue ranks and links by rearranging issues in your structures if you use the corresponding generators (Automation).
-
grant permission to a structure on user basis
As an admin I want to be able to grant permission to a structure on a user by user basis. Ideally, I would specify a list of user names. I want to have a more granular user list than project.
1 voteReleased in Structure 6.0
-
Allow Epic extensions in a NextGen project since it's not currently supported
NextGen doesn't allow for epic extensions - can you provide this?
3 votesThis suggestion has been implemented by the Next-Gen Extender, please check more details in our docs: https://wiki.almworks.com/x/Y4KlB.
-
Remive Parent(x) formula limitation
Parent(x) formula aggregation should be calculate on a sum of time spent column or another formula column
1 voteThanks! Please check the comment
-
Resource Leveling Options
Allow Gantt bars to consider an issue's "Remaining Estimate" value when computing the resource usage. Currently, we have issues with a start and end date, and are using time tracking which keeps track of "Remaining Estimate".
But the Gantt bars are allocating by default, the value of "1.0". So the quadrant for resource usage is computing a total resource need that is assuming everyone is allocated 1 full day for every assignment. If an assignee has 8 things going on in a given day, it's reporting 64 hours need by that person per day! If instead the resource usage would…
1 vote -
Show linked subtasks in Structure for Cloud
Currently Subtasks to issues cannot be displayed in Structure for cloud. It would be great to see these imported into the structure and displayed
1 voteThis feature has been implemented by the Sub-task Extender generator: https://wiki.almworks.com/x/nQMUB
-
show linked issues based on an automation rule
I'd like to add a few top-level issues and then see all other issues that are linked to those top ones via a specific issue link type
3 votesThis feature has been implemented by the Link-Extender generator: https://wiki.almworks.com/x/mLG9Aw.
-
Multiple parents within same structure
Allow an issue to have multiple parents within the same structure. My teams use JIRA to manage their messy hierarchies of requirements (vision, needs, goals, objectives, requirements, desirements, stories of all kinds, tasks, epics, bugs,... We make them all the same JIRA issue type "Requirement."). Often the same requirement "elaborates" multiple higher level requirements, so the hierarchy is messy. We have been using a custom link type of "elaborates"/"elaborated by" to represent all the requirements in the hierarchy, but it is difficult to see and manage when the messy hierarchy has many levels and issues.
1 votechange to Completed, since it is already done in Structure. Thanks!
-
Separate Effort from Duration. Gantt should show the duration independent from the effort estimation.
Duration depends of the availability of resources. Gantt should show how long the issue will take to close, For Stories the duration is given by the sprint. For Epics there is no possibility to hold this information and show it in the Gantt, using the Effort field for this information is completely the wrong way.
3 votesWith the release of Structure.Gantt 1.4 it is now possible to enter Effort and duration independently. Please, see https://wiki.almworks.com/x/C7W9Aw for more details
- Don't see your idea?