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.
173 results found
-
prevent double counting
When an issue appears multiple times in a structure (e.g. epic link and issue link),the progress calculation should be configurable to prevent / allow double counting
3 votesplease see the comments
-
provide "root element of column x" in the variable selection list of formula column editor
E.g. to calculate a percentual distribution over all rows of a structure, for the formula you need the 100% value which is typically shown on the root element.
Therefore it would make a lot of sense, to be able inside "formula column A" to use a columns B's value, but the root element value! This should be possible even if column B is a formula itself.
As we can already use variables like "Column B ..." in formulas it would be nice to add "Root Value of Column B ..." to the variable selection list3 votesThank you for the idea! Read the comment, please
-
allow filtering a centralized time period for a view with multiple worklog columns
when you report worklogs with structure, you want to use the worklog column and specify a time period.
If you add multiple columns, it is quite an effort to change the time period from eg. dates of jan to feb. (currentmonth is helpful, but somewhat too dynamic if you want to compare months)To easily switch between months it is necessary to switch the time period you look on on the view level and influence alle worklog columns this way.
3 votesThanks!please read the comment
-
Choose what group label to display and which order for field fixVersion
This idea is a to provide a way to display only (or to hide) some fixVersion instead off all of them when we use the grouping feature. If it is possible to choose the storing order (asc, dsc) it would be awesome !
3 votesthank you! check the comment, please
-
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
-
Yellow "x items selected" box shouldn't push list of tickets down when it appears
Hi! I am using version 4.6.5
When you select a ticket, the yellow "x items selected" box appears, and visually pushes the entire ticket list down so you visually "lose" the item you just clicked on.
To see the problem in action, scroll to the very bottom and select the circle for the very last ticket. Instantly, the ticket gets pushed downward and disappears, so you have to scroll down to see it again.
It's also a problem when I have some tickets selected, then do ctrl-A, ctrl-A to deselect all tickets. The yellow bar that was there goes away,…
3 votes -
Use a field (i.e. sequential index) to automatically create hierarchy into Structure when importing from CSV/Jira.
Hi, we usually load Jira items via CSV import, and it is very time consuming to arrange them with links or to manually indent them into the Structure.
It would be great to use a field like the Structure's sequential index.
For instance, using that field during import, to automatically arrange the hierarchy into the Structure (i.e., item 3.1.3 to be put automatically after 3.1.2 and underneath 3.1).Many thanks, and congrats for your works, it is very well done!
3 votesCheck the comment, please!
-
Ability to resize column widths on printable page
The column widths of the printable page are set by Structure and often ones with a lot of text (like Description or Comments) end up too wide. Would be great to be able to set widths before exporting
3 votesThank you for the request!
-
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
-
Reverse hierarchy
For instance when looking on what a team (or singel dev) is working on. I would like to expand an issue and see what motivates it.
It is possible to do with normal link types but not with epic link and sub-ask-link
So what i want to do is to create a view from the perspective of a developer. follow parents and depends on deeper. Having the story as the first layer.
Story: Build a nice landing page
- Epic: make the onboarding and retention of new customers better (reverse epic link)
- Initiative: gett 1000 new customers (link)
-…3 votesThanks, please look at the comment
-
Open issues in Jira search view
It would be helpful if you could open a folder, sub-folder or a grouping, within your structure, in the Jira search view pre-populated with the issues in folder. This would allow you to easily share specific issues in your structure with relevant engineers so that they don't have to find the issues themselves within your structure.
Examples:
Create a sub-folder and insert issues using JQL. Open all the issues in that sub folder, in a Jira search view. From the Jira search, you can easily share with team members.3 votesThank you for the suggestion. As I understand, you want to share issues from the structure somehow, right?
There is the “Sharing a Perspective” feature in Structure for Jira On-Premise. It allows you to focus a specific folder or select some issues and share this view with others in the form of a permanent link.
Would this feature solve your problem if we migrate it to Structure Cloud? You can read more about it in our wiki https://wiki.almworks.com/display/structure/Sharing+a+Perspective
-
Available resources
Limiting number of resources that can be allocated for a day to specified number.
Use case: I have two people working on a project and they can't do more that two cards at the same time.
3 votes -
Color settings for baseline bars
Now baseline bar can be only gray. If you print Gantt chart on paper it is not easy to see baseline bars.
Can you add color settings (maybe like for slices) for choosing color for baseline bars?3 votesHi Alexander! Thank you for the request, so am I getting you right that your idea is to be able to select the baseline color while exporting Gantt chart? Would making it more contrast by default help you?
-
Allow html (Jeditor) renderer for column type field
If we add new column form issue field which use Jeditor renderer(html), than in Structure table we see html tags and not the same view like at issue view page
3 votesthanks!
-
Have a structure folder be a Jira component
Would be great if this could work in 1 or both directions:
When creating a folder, I have the option of pulling a component from my component list (perhaps there could be an option to instantly pull in all existing issues in the component)
Ability to "nominate" a folder as a component (perhaps there could also be the option to add existing and newly added issues from the folder inside the structure to the Jira component)
3 votesThank you for the suggestion!
For now, folders are designed as our internal entities to structure a hierarchy. But you can use Grouper Automation by Component. https://wiki.almworks.com/display/strcloud/Field+Grouper
If Field Grouper doesn’t work for you, could you please share your use case? Why do you need to integrate folders and Jira components?
-
Colorize field depending on the value
Make it possible to colorize a field depending on the value, similar to Wiki Markup for Structure for Server/Data Center.
I want to use Structure as a dashboard to monitor project status or individual issues. Color indicators quickly highlight the status. Especially a simple green, yellow, and red colorization of the text or the panel can help a lot.
3 votes -
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?
-
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
-
Header/Footer for Print & PDFs
Add ability to edit header and/or footer for print outs. Include fields for Date/Time Printed, Structure Name, Etc.
2 voteswaiting for comment reply
-
Calculate context-aware Progress
When displaying structures in a specific context (for example, after selecting a specific Version from the Project view), the Progress roll-up should be done in the context of that version.
For example, assume I have an Epic containing multiple stories which will be completed across several releases. If I view the structure in the context of the upcoming release, it would be nice if the Progress calculation were based solely on those stories targeted for the upcoming release.
2 votes
- Don't see your idea?