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.
39 results found
-
Have a calculated "Slack" column
Structure/Gantt should have a "Slack" column that shows the number of days/weeks that a task can be delayed before any task that depends on it is delayed.
This is critical when viewing complex projects and needing to know what can be delayed when new work comes up or tasks take longer than expected.
2 votes -
Export Resource usage to excel, to generate shareable reports
I'd like to be able to share resource usage information with people not using jira.
Export to excel of the resource usage table could be useful.
Graphical and printable representations of table also could be useful.2 votesHi Andrea! An export of Resource allocation is planned to be done in one of upcoming versions. Thank you for feedback!
-
Respect dates of future sprints
We want to plan projects using team sprints.
In the documentation https://wiki.almworks.com/display/gantt/Planning+with+Sprints you say:
Jira does not allow you to specify dates for future sprints, so Structure.Gantt schedules future sprints based on your Sprint configuration settings.
This is not true, we can specify dates of future sprints but Structure seems to ignore the dates.
2 votesHi Michael!
You’re right, starting from Jira 8.3 it is now possible to specify dates for future sprints, we’re going to support this in one of upcoming releases!
Thank you for feedback!
-
Show additional information on the ressources panel
The ressource panel only indicates the ressource name. For supporting scheduling It would be very helpful to have more information directly in the ressource panel, e.g. "Units", used calendar and a marker or counter that x availability periods are aligned to the respective resource.
1 voteHi!
Thank you for a suggestion. Showing more info is indeed a good idea and it is actually planned.
-
Gantt for Cloud: Sort on scheduled date
The only sort functionality is by using issues fields. However, when using gantt, sorting by the configure start date field, it doesn't provide always good sorting when some issues have a start date and other issues are being scheduled automatically and would result in an earlier schedule start date than the manual entered start date.
Hence,
- sorting can be done on issues with a manual start date
- sorting is automatically done for issues with a auto-scheduled start dateBut: sorting cannot be done between manual & auto-scheduled issues
1 vote -
Presentation Mode for pausing redraw and updates, BIG fonts, make the sprints more obvious
We would like a Presentation Mode for the Gantt chart view that does the following:
1) Pauses all updates, no redraw, no refresh, no live changes
2) Makes the fonts for sprint and calendar dates much larger and easier to read (this could also be an accessibility settings in Configuration)
3) Make it faster and easier to see the sprints on the timeline think about color coding. Offer a way to toggle between calendar view and sprint view or faster navigation around the Gantt chart, like a "jump to sprint x" or a "zoom to details" button.
1 vote -
Share lag values across all structures
Dependencies are stored in Jira as linked issues, but there's no concept of "Lag" (eg: TaskB can only start 1w after TaskA finishes), so that's stored in the Gantt.
We have a main structure/gantt for all work (so we can see full utilization and dependencies), and people create their own structures just to see their team's work in a specific format (possibly even changing resource attribute).
PROBLEM: A user adds a dependency with lag in one structure, and the dependency shows up in the other structutre, but without the lag!
SOLUTION: Be able to store lag info in Jira somewhere?…
1 vote -
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 -
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 -
Allow dependency linking to tasks not in the Gantt view
When trying to create a new dependency link for an item by clicking on the little dot beside the item in Gantt view it would be beneficial to be able to link to items which are not visible in the Gantt view. This is especially useful when using transforms which may filter items from the view but you still want to link to the hidden items.
1 vote -
Reduce the margin/padding of every row to increase the level of entries visible in the screen
Gantt charts are a good tools to see the globality of the project at once.
Having a layout mode like: compact/confortable would be very interesting to maximized the visible content while looking at the dependencies in the gantt chart.1 vote -
Allow multiple resource to work on one item
As a user I would like to have more than one resource to work on a task, especially when doing macro planning and integration task that require multiple team to work together in one item.
1 vote -
Improve Sandbox feature capabilities
Latest version of sandbox with 3.0.1 is limited in its re-planning capabilities. Some changes require removing tasks and adding new tasks for change requests from Marketing. Need to add support for:
Changing links between tasks
Ability to add new tasks as a change requests and change linkage between resources
Ability to remove tasks as a trade off for a change request
Move tasks between groupings and relink with other tasks because of unexpected issuesIn all cases, most changes are to view how a change request or trade will effect a schedule before marketing and team commits to the changes.…
1 vote -
Be able to print issues attributes summed over time
As a user I would like to monitor the evolution over time of a numerical issue attribute value summed across issues and displayed it like ressource usage are displayed.
Example : attribute cost of a story to monitor cashflow over time.
1 vote -
add hash marks to the parent bar in Gantt based on child dates
Allow the ability to add hash marks to the parent time bar in Gantt based on child dates. This would allow to see milestones without cluttering the view with multiple child issues.
1 voteHi Jamie!
Thank you for a suggestion and a feedback!
-
Posibillity to shift more issues at once in the timeline
Our organization would like to have a feature which would let us to move few issues at once. F.e.:
Epic has issues inside. So if I move the Epic bar, all those issues inside epic would move the same. Like in Jira's Advanced Roadmaps1 voteThank you for your suggestion. This feature is frequently requested, and we hope to start working on it soon. If there’s something we can help you with, fell free to ask.
-
Hide the days and unworkable hours of the gantt grid. Especially when it is extended to the maximum (hours)
When the maximum detailing of the gantt chart is done, the days and hours that do not end up representing a greater amount of columns in the gantt. It would be much more practical with great visualization without these columns. Especially when there is a need to visualize tasks that are defined with small loads of hours and to be executed on the same day.
1 voteHi Milson!
Thank you for your answers!
-
Track a chain of linked issues
You want to track a chain of linked (dependent) issues through a large structure. It would be useful to highlight predecessors and succesors of a given issue by issue link using, for example, colors.
1 vote -
0 votes
Hi Steffen,
can you be more specific, please? What kind of connectivity you wish to be implemented? What are your use cases?
Thank you!
Regards,
Alexey
- Don't see your idea?