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
-
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 -
Add sequence or ID for Issue Item Property
It would be helpful if the "ID" would be available as an Issue Item Property, similarly as key or summary etc.
It would be useful for example: As an admin I need to go to database and find some rows in tables that are using issue id as a reference column.
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 -
Ability to automatically show blocked stories or features in RED
I would like to make blocked stories and/or features visible in the gantt chart by showing them in RED or some other indicator where they stand out.
1 vote -
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 -
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!
-
Allow multiple slices to affect an item if they target different sections
In the Gantt view, when using slices, it would be great if you could have "stacking" slices as long as they don't target the same section. For example, in one of my Structure views I have a slice that auto-configures Tasks to be Milestones if they have a date in a specific field. I also want to be able to color code all non-Epic items based on their status, which would be 4 other slices, but if I wanted to apply this to Milestone Tasks I would need to make 4 additional slices to accomplish that.
1 vote -
Support variables / formulas global to a view or structure
In Structure 8.2.0, you introduced the ability to save and share formulas. Once the formula is loaded, it is stored to the new column and not impacted by any changes to the source formula.
This does not any real-time if the formula has been shared in many locations. Updating a variable formula involves several steps (not sure reloading is much quicker).
It is also a quality risk because the user has to make sure any updates have been made everywhere. it takes several steps to verify the updates were made.
variables/formulas global to a view or structure would support the…
8 votes -
Alerts/Warning where issues doesn't completed according to their related fixversion release date
Alerts/Warning where issues doesn't completed according to their related fixversion release date
1 vote -
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?
-
Support Parameters (per structure) for transformations
Basically I create a structure per version of my application and I use automation to insert issues based on certain filters that are for the given version (e.g. bugs with certain properties for this version etc...). Not everything is inserted by automation, but there are several places where I use automation for inserting. Thus every time I create a new version, I have to "find" all these insert automations and modify their filter to match the new version: Not really a problem, but it would be very nice if I could somehow specify the version as an attribute of the…
3 votes -
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.
-
Add ability to Extend by Formula
Grouping by the result of Formula is very robust - it is possible to produce literals as well as arrays.
If it wolud be possible to Extend by Formula instead of the links and subtasks and Epics only, it would give the power of extending based on the content of the Jira ticket, which may contain i.e. fields with issue list.
It would by possible to construct deep structures with issues not linked to other issues but having them listed in some fields.1 vote -
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 -
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 -
Place filters above column headings
The filters section for a Structure should be placed above the column headings section. This allows the column headings to be directly above the content of the Structure rather than being separated by the filters as it is now. The current configuration is unintuitive and difficult to read.
1 vote -
Allow customization of the Appearance of Groups in Structure.Gantt
I would like to be able to customize the Appearance of parents that are treated as groups. When that option is turned on, the parent becomes represented in the Gantt as a bracket. When I don't want to expand the structure to a level that includes the child tasks, I would like to see those brackets as bars.
6 votes -
Integration with insight
The step forward for structure development - adding a posibility to work with insight objects inside formulas or in more UX attractive way. Such integration will provide unlimited power for structure to produce any type of dashboard / timeline / resource plan etc.
5 votes
- Don't see your idea?