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.
63 results found
-
Quick Grouping and Sorting
Currently we can only use quick filters. The most used feature in our customer projects (datacenter) is the quick group feature.
This feature should be available on structure cloud as well, because it makes the use of structures so much more flexible and enhances the usability.
Currently our users create a lot of new structures just because of this missing feature. Obviously this leads to maintenance issues, because all other configurations need to applied across multiple structures...Same goes for Quick Sorting, but the grouping option is more important.
9 votesHi Martin,
With the latest update, we've added quick grouping capabilities. Sorting by a column is already available for our users. Please, take a look and let us know if it solves your use case.
Quick groups:
https://wiki.almworks.com/documentation/structure/9.0/cloud/quick-groups-187662723.html
Sorting by columns:
https://wiki.almworks.com/documentation/structure/9.0/cloud/sorting-by-columns-157319184.html
-
Allow entering list values on separate table rows
It would be nice to have options of single and multi-select list fields optionally displayed in different rows.
2 votesHi Dimitrios,
Thank you for the request. Could you please clarify a little what do you mean by select fields displayed in rows?
Is it about Jira fields? Do you want them to be in rows, but not columns? How would you like to use it and why?
Thank you,
Konstantin
-
Add select list options to different table rows
It would be nice to have options of single and multi-select list fields optionally displayed in different rows.
1 vote -
Allow users to select any task/milestone and see its critical path
There are various reasons why this is essential for large or interdependent projects:
Large projects often have multiple future milestones at fixed points. We don't often want to view the critical path of the future-most milestone, we mostly want the next upcoming milestone. We can exclude milestones except for the upcoming one, but then we need to keep adjusting the structure, and we can't see all the milestones at once (eg: maybe the next milestone after is also at risk).
Our projects invariably have inter-project dependencies. At the very least, the dependencies are resource-based (eg: we're sharing resources between projects).…
2 votes -
Gannt Presenation View
The view in the GAnnt musty have a way to be presented with in the screen. it is haed to work in a status meeting and use the gannt
1 vote -
Group by Formula
Have issues in your hierarchy grouped by a specific formula using a new generator.
12 votes -
Improve loading of large structures (30k+)
Improve loading of large structures (30k+)
4 votes -
Performance/Stability: Fine-grained LSS
Performance/Stability: Fine-grained LSS
4 votes -
Formula: Use complex variables in formula: Columns, Formulas
Be able to use the same functionality available in Structure Server/DC formula columns in Structure Cloud (column as a variable, etc...).
4 votes -
Support cloning a Structure and its Jira issues on Cloud
On Structure Server/Data Center it is possible to clone a Structure and its issues into a new Structure with new issues. This functionality should be supported on Cloud as well.
4 votes -
Manual adjustments to automated structures in cloud
We want a structure where automation is used to fetch issues, but where we manually sort issues into a hierarchy of folders.
It can be done using metadata for issues, but that has two drawbacks:
1. It can be quite tedious to update metadata to get the issue into the right folder
2. If someone "else" updates the metadata the issue will move immediately. We what to do the moving manually in status meetings/during grooming.1 voteHi Lars,
Thank you for your request.
Could you please share a little bit more details so we could learn more about your scenario? Why do you need automation to fetch issues, and adding them manually and moving between folders won't work for you?
-
Add support for issueLinks in formulas
In the data senter version of structure you have support for issueLinks. After moving to cloud this is highly missed as it is an extremely useful feature to fetch data from linked issues, like due date of blocker issues.
3 votesHi Lars,
Thank you for your request!
We are working on formula improvements and this feature is indeed in our backlog.
-
Calculated Columns: Number & Currency Formatting
Formatting option for values in a numeric columns (e.g. have numbers with a thousand commas by default)
User case: for currency value, use a thousand commas.
Format dry numbers to show as normal dollar amounts -US Example:
with dollar sign and commas = $ 1,350,500.43
South Africa Example:
with R and spaces = R 1 350 500.433 votes -
Group by Generator: Add option to display empty group
Add the option to show empty groups when grouping by a field.
For example, I group by assignee. I still want to see folders with all the assignee names even tho there are no issues assigned to them.
1 vote -
Earn Value Management Formulas
Formulas for project tracking: Earn Value, Cost Performance Index, Schedule Performance Index, Estimate at completion, etc using cost from Tempo
6 votes -
Support JIRA Discovery links
Recently JIRA introduced a new project template "JIRA Discovery".
Tickets ("Ideas") in JIRA discovery can be linked to other project tickets with a special dependency called "Implements". This type of links is not supported by Structure yet but it would be extremely helpful to see Ideas' delivery breakdown in Structure.1 voteHi Semeon,
Thank you for the idea!
-
Tempo Hours in Structure: Budget (planning) - Actuals (logged) - ETC (remaining)
As a Project manager, it's handy if the hours are visible in Mandays or Hours to check the financials. 3 columns if (not yet already available to see the Tempo Hours in Structure cloud: Budget (planning) - Actuals (logged) - ETC (remaining). And this is for each separate issue type and rolled-up based on hierarchy or grouping. And visible or reported not in weeks but accumulate in mandays and/or hours. Tom
3 votesHi Tom,
Thank you for your request.
I see that you require your columns to be in a specific format.
But could you please clarify, do you have the Budget (planning) column already or do you want it to be implemented? If you already have the Budget column, is it just a custom field in Jira?
Thank you,
Konstantin
-
work logged (in maydays)
Now the field 'tempo work logged' calculates the time logged in: xW + xD + xH etc. Can you also make time summed as 'x Mandays' or 'x Hours' as calculating in weeks is not easy to calculate a budget. From project management perspective its better to have a start and finish date a.k.a lead time AND the time (hours or days) spent in mandays to very the budget.
3 votesHi Tom,
Thank you for your request.
Could you please clarify, how you make calculations on the work-logged data? Do you export structures to Excel first?
-
In JIRA Cloud create a saved filter for issues in a structure to be used in boards
It's easy to collect all the relevant issues from multiple projects into a single structure but it's very difficult to create a JQL filter that contains the same issues to be used in other parts of JIRA.
As a user of JIRA Cloud I wish to be able to use JQL to search "Issues in Structure (XYZ)" to get all the issues within the XYZ structure
The functionality that is available in On-Premise Version
3 votesHi Alex,
Thank you for your suggestion.
Unfortunately, custom JQL functions are not currently supported in Jira Cloud, so migrating S-JQL in its current form is not possible.
We are monitoring updates from Atlassian on this matter.
-
Usage logs (cloud)
As an admin, I'd like to see more than who owns a structure, I'd like to know how often it is used (accessed, changes, number of users or permissions settings. It would help with maintenance and upkeep of structures over time. Additionally it seems DC/Server has ability to view history which would be nice, that is not available in cloud
3 votes
- Don't see your idea?