Roadmap Layout Feedback

[rileybroughten]

Thank you for trying the Roadmap layout in Projects! Check out the documentation for more information.

If you encounter any issues or have suggestions on how we can improve the experience, please share below.

[ghost]

I was attempting to use the Show and Hide Fields feature, but it did not appear to do anything.

The documentation indicates this controls what is shown in the side panel, but it would be more useful to have fields shown as additional columns like the List view does.

[rileybroughten]

👋 Thank you @andrew-motus for the feedback! You are correct that for now, toggling the visible and hidden fields only affects the fields that are visible vs contained in the Show all fields expansion when you open up an issue in the side-panel, as shown below. The date fields selected for the roadmap view are automatically selected so that they are visible by default to make edits easier.

We are still exploring what this menu option could represent to be able to toggle additional field information directly on the roadmap, so we will keep you posted and update documentation as needed as this may change in the future! 👍

[rileybroughten]

HI @andrew-motus - just following up that we have since disabled the Fields menu as all project fields are now shown by default in the project item side-panel 👍

[opus131]

@rileybroughten I have received an invite last night but it's not for the account/organization I applied for.
I now have access to the roadmap feature, but only in the dormant org that does not have any projects.
I tried to select the correct org again on the waitlist page, but it now says:

Please could you change the org for me so I can start using the feature?

[opus131]

Thank you @rileybroughten, the org name is 2iq

[rileybroughten]

@opus131 just enabled 2iq, you should see access come through within a couple hours!

[mariusc23]

@rileybroughten Hi! I have a similar issue. I got access to the product roadmap beta but I was also interested in the Tasklist beta. I get this same error when I try to sign up for the Tasklist beta.

[rileybroughten]

@mariusc23 are you still seeing this issue, and if so what is the organization name? cc @omerbensaadon to look into 👀

[mariusc23]

I received an invite to the Tasklists beta yesterday so this is no longer an issue. Thanks for checking!

[itwasmattgregg]

It would be AMAZING if you could assign an issue to more than one iteration.

[janpio]

This works.

It's a bit awkward to have to manage iterations twice, but maybe persistent usage this way is a signal that the UI should maybe be able to use the same Iteration field as separate Start and End settings in an issue (so: 2 separate dropdowns as we get when having to unconnected iteration fields). Could be a setting of the iteration "Separate Start and End setting on issues" or similar. Then this would also be possible here.

[dalechyn]

Absolute yes. Works now as a hack, but will be hard to manage two iterations if something "goes unplanned".

[colespencer1453]

@rileybroughten My hope is that this gets integrated with tracks and tracked by that is currently in development. The best use case I have for a roadmap view like this is showing expected feature delivery dates which can span multiple sprints since user stories can be smaller shippable units of work.

My preferred behavior is that once there is a parent child hierarchy with tracks and tracked by that you can filter on a "feature" label and show the stories a feature spans based off the iterations of it's child issues.

I know this behavior is somewhat complicated, but that is the only behavior I would use this view for.

[rileybroughten]

@colespencer1453 are you using an iteration field as the Date fields on your roadmap? Does the cumulative timespan help with this when you are grouping by a field (Tracked by), where it shows the full duration of items within a group?

[colespencer1453]

I don't yet have access to the Tracked By Private Beta. We have applied for organization access. Can't wait to see it though!

[minhho-itr]

Because we could add multiple date fields. So, in my opinion, it would be better if github team can show the interim dates in the gantt chart, something like this:

[rileybroughten]

@minhho-itr thank you for the feedback! Given you can currently specify one or two date/iteration fields, we are still thinking about how to best support additional dates 👍

[e8-MattLoidolt]

Adding feedback thoughts to this: It would be great to have a higher level grouping like this, especially for projects at the org level (not at a repo level)

Currently tough to do since milestones are just at a repo level, and it seems like the natural grouping would always be by milestone (but maybe it could just be to select any 'group by' custom field you want)

[rileybroughten]

@e8-MattLoidolt here is the documentation for grouping on the roadmap layout, as you can group by project-level custom fields as well as milestone, repository, etc. Let me know if you have additional feedback here for improvements!

[checkdigits]

Nice work!

It would be useful to be able to have some sort of shading or hatching for non-working days - or at the very least weekends. Since this timeline view is likely to be useful for visualizing the task data to non-expert users who want to answer questions like "how many working days is this expected to take" and "can we ship it before next Friday's demo?"

Also a day indicator such as "Mo", "Tu", etc above the dates so that it's more obvious when a particular item is planned to be finished.

We often have conversation with product owners who say things like "so will it be ready by next Thursday" and, as they are very visual learners, it would be nice to be able to show them this view.

Right now the grid is a bit non-obvious 'at a glance', especially in dark mode (which is my default).

Note the red boxes I have drawn around the otherwise invisible weekends.

[rileybroughten]

Ah my mistake! There is no exact timing on configuring the workdays yet, but I will keep you posted once we have a timeline for this 👍

[derbl4ck]

Alright, thanks a lot :)

maybe offtopic: I would love it if the "Team Capacity" feature from Azure DevOps could also be available for GitHub Projects. Then, for example, all items on the roadmap for which no capacity is left could be deposited in a certain shade. Another idea would be that the length of an item in the roadmap is aligned by default based on the estimated duration of a Item.

[rileybroughten]

@derbl4ck thanks for the feedback - will bring back to the team 😁 For now you can utilize displaying the sum of numeric fields on the group headers for each of your views 👍

[lukens]

Just saying I agree that shading for weekends, and weekday headings, really would be very very useful.

[isanchez-ng]

I also agree on shading or hiding the weekends @rileybroughten ! Is there any news about it yet?

[checkdigits]

It seems to be more visually appealing (if you're a weirdo like me) if the "dots" for the issue were aligned with the line for the current day column indicator.

At the moment they are aligned to the left of the line. 🤪

The status circles even have a nice dot in the middle of them they could be aligned to.

So, something like the following:

[rileybroughten]

Thank you @checkdigits for the feedback and details! Will take this back to the team 😀

[KevinRaney]

Is this feature ever going to be available to user accounts or just organization accounts?

[rileybroughten]

Hi @KevinRaney, we are still working through the Private Beta waitlist where organizations have registered, so if you are part of an organization then the org admin can help with registering through the waitlist! I will provide you with an update once we are past this point, but yes it will definitely be available to both user and organization accounts!

[rileybroughten]

Providing an update that we are now in Private Beta so @KevinRaney your username should now have access 😁

[sschuberth]

Please add "months" as a duration for iterations. Use case: We'd like to create a coarse roadmap that just highlights which issue is planned for which quarter of the year. Having a "months" duration would make it easier to define a "Quarter" iteration to assign issues to, esp. as iterations get auto-numbered. In the current state, when choosing 12 weeks for a quarter, "Quarter 2" does not start exactly on April 1st.

[rileybroughten]

👋 Thanks for the feedback @sschuberth! We understand that an iteration duration period past days and weeks would be very helpful for cases like this when you are trying to represent a longer time frame for higher level planning. We have this feedback item on our backlog and will keep you posted with updates 👍

[ashleybot]

@sschuberth I'm not sure if it helps while you're waiting, but I have mine configured as as an iteration is 13 weeks and the quarters start and end where I expect. Then my roadmap view date fields are set for iteration start and end and it seems that everything is displayed correctly.

[sschuberth]

Thanks. I've actually manually adjusted each iteration's dates meanwhile, which also works for now.

[duckinator]

I just went to set up a roadmap with monthly iterations and found I had to manually adjust them. If the duration options were X {days,weeks,months} instead of X {days,weeks}, it'd make that a lot less tedious.

[timja]

We have multiple teams that work from one roadmap and I can't see how to make that work here, we're currently using multiple sprints at the same time for that to work in Azure DevOps, but the GitHub projects don't allow you to have an iteration running at the same time.

We have this sort of view along the left hand side in Azure DevOps:

I can't see anyway to separate out different teams work (to stakeholders it wouldn't matter but for internal use making.

I tried with labels but it doesn't show up on the card. Grouping by iteration is close to the view we had on ADO but it would be good to be able to group on a second field or have multiple iterations with the same dates.

[jayspadie]

@timja I'm not sure I completely understand the scenario, but would it be helpful to consider these options?

• Create multiple Roadmap views, and apply a filter to each to limit the rendered items to Red, Yellow, or Blue epics.
• Use two iteration fields called Start Sprint and End Sprint, as described in this comment if epics span multiple sprints.

[timja]

Create multiple Roadmap views, and apply a filter to each to limit the rendered items to Red, Yellow, or Blue epics.

Thanks that seems to work fine, a little bit different but I wouldn't like to ask for just the same. I added a label filter on each view.

Use two iteration fields called Start Sprint and End Sprint, as described in this comment if epics span multiple sprints.

Not tested but this looks perfect thanks

[OneCyrus]

what i thought would be a core feature is visual support of the issue hierarchy. using those "tracked by" and "tracks" fields in the roadmap view should enable things like:

• parent "issues" should at least auto-cover the timeframe of all childs
• show me lines (or something similiar) to visualize which issues are tracked by another issue
• IMHO there should also be a "depends on" field to track things which need to wait for another issue

[OneCyrus]

@rileybroughten yes, grouping works to some degree. but it has some downsides like not being able to use something else to group and having the parent issue in another group.

• If there aren't dates defined for the "parent" issue (where the tasklist is defined), would you expect or want dates to be auto-populated/added to the parent, that cover the timeframe of all children issues?

It would be great to have dynamic dates for the parent. basically inherit from the childs without setting a specific date on the parent. but I guess your current data model needs to have concrete values set to the issue. if it could inherit from the childs it could be overridden with a concrete date on the parent issue. it would allow to break the inheritance. otherwise yes, auto add the date from the childs.

• If the date of a "child" issue extends beyond its original estimate, how would you like this to reflect in the "parent" issue, if at all?
  if we have a specific end date on the parent it should show a warning (e.g. exclamation symbol on the field) that the scope of this issue will take longer than planned.

[colespencer1453]

Adding to this that this is the only way I would see the timeline view as useful is if it supported this parented grouping behavior where the parent shows the iteration of all of it's child issues that are tracks on the parent.

[derbl4ck]

@rileybroughten do we have news about the desired "depends on" field?

I would love to have a field where I can reference one or more issues that need to be done before an issue can be processed. This information is also absolutely interesting and helpful for a timeline like the roadmap feature. This could be interesting for many enterprise customers as a currently missing feature to switch from Azure DevOps / Jira / GitLab to GitHub.

[rileybroughten]

@derbl4ck There is not an update on a dependent relationship type. We definitely see your and other's use case here for being able to sequence items across Projects, and especially with roadmap being able to visualize what works comes first and what comes after. I'll provide an update when I have one, and please continue to share thoughts or feedback as you're using roadmaps!

[dominicafonso-datum]

@rileybroughten is there any news on dependencies within issues to improve the roadmap view.

[janpio]

Someone already using roadmaps in a public project in a nice way? It always helps me to see how others use a new feature to understand what it is really capable of and how I could use it myself. Just leave the link in a comment here.

[checkdigits]

We are using it in a way which is only public to our organization - I'd be happy to share a screenshot or something with you privately if it was helpful to you.

[janpio]

Absolutely - my first name @ prisma.io will work. Thanks!

[checkdigits]

Emailed you.

[bewuethr]

I use them on a hobby project for a website that I maintain, basically as a way for me to see what I worked on and when via assigning issues to week-long iterations: https://github.com/orgs/swissclubto/projects/1/views/5

[Arend-MI]

• It would be nice if we could visualize the (due date of) repository milestones in the roadmap timeline as a vertical bar or otherwise. Then one can look at the milestone due date while planning the work (either on 'epic' level or the issues). Note that I did try the grouping option for milestones, but then you loose the ability to group based on another field and via this way the (embedded) milestone due date is not considered / visualized.
• I would love to be able to fold/unfold any "child issues" within the roadmap view (and other views actually) without making use of the grouping option in order to clear up the current view and consider higher-level issues only. This could just be a local control directly located at the parent issue within the board layout. Not sure if this functionality will be included in the tasklist ([Private Beta] Tasklist Feedback #39106, requested access to private beta).

[Arend-MI]

@Arend-MI we are currently exploring exposing milestones in the roadmap! A question for you: would you expect to display all milestones that are associated with the items in your project, or toggle specific ones?

@rileybroughten To have them in the roadmap layout would be great, to also have control over their (individual) visibility would be superb :)

[jrhemstad]

After working with this some more, I've actually come to realize that with the addition of task lists that Milestones are really no longer needed.

Instead of a milestone I can just create a "Epic" issue that lists all of the issues I would have put in the Milestone. This already has the advantage of the fact that I can have sub-issues from different repos, which I can't do with Milestones. Furthermore, because the parent issue is still just a regular issue, it is already visualized in the roadmap timeline like I'd want.

[rileybroughten]

You can now display a vertical marker for milestones associated with your project items - feel free to give it a try and let us know your thoughts!

[ifiokjr]

@rileybroughten this is great. I'm using this feature.

Right now, when grouping a roadmap by milestones, the milestones are automatically sorted alphabetically, I would like an option to sort the milestones by due date. This seems to be a more intuitive way of sorting the groupings.

[dominicafonso-datum]

@rileybroughten this is great. I'm using this feature.

Right now, when grouping a roadmap by milestones, the milestones are automatically sorted alphabetically, I would like an option to sort the milestones by due date. This seems to be a more intuitive way of sorting the groupings.

this is why I came here. Sorting milestone sby end data makes the milestone end date useful.

[jrhemstad]

As I'm planning out the roadmap for my project over the next year, I'd love the ability to specify a duration for a task without assigning it a particular start/end date right away.

In short, I've got a big list of tasks for the year and I know roughly how much time each task will take, but I don't know exactly when I want to start each task. I'd love to be able to just quickly populate the roadmap with a bunch of tasks and assign a duration to each task. Then I can just drag&drop tasks around on the timeline to determine the start/end dates automatically.

For context, I'm coming from using Google Sheet's timeline view that has this option of specifying a start/end date or a duration. It would be nice to carry over the ability to optionally include or exclude weekends when using a duration instead of start/end date.

[checkdigits]

This is an excellent idea for me too. If there's an automatic end date based on a start date and anticipated duration it would mean you can drag around items on the timeline and see the effect on the end dates on the item itself too.

[rileybroughten]

@jrhemstad noted these for feedback 👍

In the meantime, you can also use iterations on the roadmap layout to specify dates for your items, if this helps for cases where you want to use a "bucket" of time rather than specific dates when initially populated your roadmap items

[checkdigits]

It would really cool if we could make the outline or background of an item change color based on the value of a custom date field.

For example, being able to make the border of an item go red if today's date is greater than an "expected end date" would give viewers a vey quick indication of those items which were overdue.

Currently it's tricky to visualize that kind of data...

[Arend-MI]

I would also love to have this feature. It would for sure benefit the status tracking possibilities in the roadmap layout.

[rileybroughten]

Thanks for the details and screenshots. Adding colors across Projects is in the works, and we are thinking about how to surface upcoming dates or deadlines to convey how things are on or off track! Will take this back to the team 👍

[derbl4ck]

@rileybroughten Any estimate yet on when this feature "adding colors to Roadmap Layout Items which exceed deadline" will be available?

[rileybroughten]

@derbl4ck Unfortunately, no estimate on this one yet. A couple questions for you on this topic:

• Are there any other visual indicators or ways you would like to see this type of information when things are ahead of schedule or fall behind?
• How would you like to see the roadmap items highlighted and colored?
• Are there any other use cases where you would like to see more color on the roadmap and the items? We recently shipped colors and descriptions for single-select fields, but that would only appear on the roadmap in the group headers, not on the pills themselves.

[peterdudfield]

I would also be interested in this. For me,
the colours would be about grouping the issues into different skill sets. I already group by geographical area.
happy with the edge being highlighted, or the background being filled.

[tomparkp]

The UX feels a bit non-ideal for roadmap items that don't contain very short titles. Previously we've named things in the roadmap titles like "Improved Venues Page" but we found that to be a bit vague and over time our roadmap would repeat the same topics so we've been trying more descriptive titles like "Expand venue pages to include additional information".

This creates a lot of clipping and applies to things like iterations as well, using an approach very similar to Github's own public roadmap creates a lot of clipping within this view:

Allowing resizing/toggling of the side panel would probably help, as well as maybe a better visual for items in which the title overruns the duration.

[ashleybot]

@tomparkp Teach me your ways! How are you grouping items in the left pane? I see where to sort, but I don't see where to group by.

[rileybroughten]

Hello @tomparkp 👋 the ability to resize this table is coming soon! 👀 We will keep you posted with updates on this, as that will help with some of the truncation issues you are seeing

[dragos240]

Could you just use ... to represent it trailing off if there's not enough horizontal space? That would eliminate the clipping issue. Maybe have the full title visible on hover.

[rileybroughten]

@tomparkp just wanted to note that you can now resize the table to configure the space on your roadmap! You can hover over the table boundary to grab and resize. Let us know your thoughts and how this helps!

@ashleybot you can select the grouping field in the dropdown below, see the docs for more details

[Davsarper]

Hi! We have started to use roadmaps, a main purpose of it is to see the actual team workload for a given period. We have added a field for effort (in FTEs as a number) and use the Sum feature to show the total FTE by team (or whatever we filter by), problem is that it sums all issues (ongoing or future) but it would be awesome for it to sum only within the visible dates so we quickly see what the workload is at any given point.

I have a separate table view and by filtering Planned or Ongoing issues I am able to get close to what we want, as I can know the current and future workload. Yet it is not exactly what we really want, what we would like is the workload at any month, quarter... by changing the time period we are observing.

[mtcA6]

I'd love to be able to group by the 'tracked by' AND reorder those things in the roadmap view so i can see the component parts of that tracking item.

Right now i can look at "epics" the things tracking other things and map out timing of things but I can't see the work nested under it

I can group by those "epics" but then I lose the ordering that I have in the prior screenshot

[nijikokun]

Just ran into this 👍 It's unclear how these are sorted.

Would love to be able to have Sort By / Sorting affect the Tracked By "epics".

[mtcA6]

There's. Whole slew of issues when using the tracked by

I think another thread mentioned that it's sorted by the ID so I think the oldest ticket/issue is the first thing you see.

Related, It would help immensely if adding work in a project automatically added the issue nested on/under the right parent issue in this screen. When using this tracked by field and adding work it will disappear from view which isn't great.

Essentially my sorting IN the issue IN the task list should carry over to the project and vice versa. As should adding and removing items

[stepashka]

I would like to understand if the projects planned for a team actually fit in their capacity.

Perhaps this could be done via the the roadmap view?

Given that issues would have a numerical field for measuring effort in days, weeks or months, I would like to be able to sum up the that effort across all the issues on the roadmap canvas and see the effort numbers for each week, month or a quarter of the timeline.

Ideally, I would like the effort sum per priod to properly account for the situations when a project can span 2 months, but the effort is actually 1 month, so for each individual month this project would contribute with 0.5 person-month 🙄

[mtcA6]

Couldn't you use a numerical field and track:
Estimated months
Actual months
Estimated weeks
Actual weeks

Etc

[Davsarper]

I'm on a very very similar situation, I have effort for issues and they sum alright in the roadmap view but cannot play wiht the sum to be by period or even ongoing (part of this period/iteration)

[rileybroughten]

While you can't sum the numerical fields by the the Zoom level of your roadmap (month, quarter, year), if you are using an iteration field, you could group by that field with the field sum displayed, as show here:

[stepashka]

Another use case is for understanding the critical paths, for identifying the latest Start date and the earliest possible Target date for projects based on their effort estimates.

For this In the roadmap view I would like to use the numeric field for defining the size of an item on the canvas.

When rendering an issue on the project canvas, I would like to..

• use 'Start date' + 'Numeric field * days/weeks/months' as the 'Target date'
• or use the 'Target date - Numeric field * days/weeks/months' for the 'Start date'

[ShrikantPati]

Can we have date fields scoped to the issue rather than the project ? so that we can have the same issue dynamically updated in multiple roadmaps.

Steps followed to test this scenario

• created two project boards - (Project board test template 1 and project board test template 2)
• added some issues to the projects and added them to a roadmap view
• Now moving dates of those GH issues in one project roadmap should be reflected in the other(s) but its not reflecting.

Screen shot

Since its the same GH issue we are referring to the expectation is If i change the start date / End of the GH issue in one project board/roadmap view the same should be reflected in the other project board/roadmap view but its not. It still shows 2 different dates for the same GH issue because the date fields are tied to the project board and not the actual GH issue.

[mtcA6]

100000000000 times agree

[chancez]

I really wish we could include the repository name in the nodes of the roadmap layout. If I have a bunch of products with GH issues like "release 1.2.0" I cannot tell what GH repo each issue corresponds to.

[kirkbushell]

To be honest, I tried to use the roadmap feature, and couldn't figure out how to actually use it. I can't understand why I can't just drag-and-drop issues onto the roadmap, and have it set the dates. Played with it for 10-15 minutes, as I'm looking for a Trello replacement and liked the idea of having everything in GitHub, but the user experience and UI is absolutely awful.

The team would do well to leverage what Trello has done well. Projects feels like a system designed by engineers rather than product/ux designers.

[lukens]

I couldn't figure it out for ages. However, I eventually worked out that you can (pretty much) do what you want, but you first have to create some date fields. Create one called Start Date then one called End Date, and then you can just add items to the roadmap, and can drag their start and ends, and it will set the dates for you.

I would agree that it is not at all intuitive.

[silopolis]

Allow to have iteration PLUS start AND target fields columns.

[lukens]

Discussion #51482 raised the problem of needing to move multiple items on a roadmap, and there currently being no means to do so. @rileybroughten said they had moved the discussion to the more general roadmap feedback discussion (which I assume is this), but I can't find it on here.

As far as I can tell this still isn't possible, but seems like something that would be incredibly commonly needed, and as with @timuric, who raised it originally, this is pretty much a blocker for us being able to use this feature.

[bpbradley]

I honestly don't see how it can be used at all without this feature. Our project is already completely broken due to small delays, and its more work than it's worth to try to fix it.

@rileybroughten is there an update on this? It doesn't seem like it should be that difficult to just select multiple items when dragging an issue to a new date.

[dominicafonso-datum]

Is there a way to enable markers by default. I'd always like to have the milestone markers visible.

[rileybroughten]

If you duplicate an existing roadmap view they will carry over, otherwise for a roadmap you'll need to enable them and save them for your view.

[Uerum18]

Hi community.
Is it possible to show issue progress on the roadmap, in case it has multiple tasks included?
I mean this counter we can see in the issues tab.

[lukens]

It would be goof if the current day indicator automatically updated.

I keep thinking I have more time left on a task than I actually do, because I go to my tab with the roadmap open, and see there are still several days left on a task. I then realise the red line indicating the current day hasn't moved on since I last loaded the page a few days ago, and I hit refresh, and things no longer look quite so on track.

[Hirotaka39]

Hi community.
I have always used Roadmap, but I would like to do horizontal scrolling by dragging the mouse, like in trello for example.
The reason for this is as follows.

system requirements

OS: windows 11
Browser: chrome

reason

First of all, there are currently 5 ways to do horizontal scrolling in roadmap. (If there are others, please let me know)

1. Press the "scroll to next/previous date range" button.
2. Tilt the mouse.
3. Hold down the Shift key while wheeling.
4. Use the horizontal scroll bar of the browser.
5. Use the arrow keys.

However, all of these methods are a bit awkward to use.

1. too large for the smallest unit of movement.
2. (maybe it's a chrome issue), the movement has a lingering effect that makes it difficult to use.
3. requires the use of both hands.
4. you have to use the mouse to aim at the bar.
5. too small for the smallest unit of movement.

Thank you for reading.

[lukens]

Just to note on this that horizontal scrolling currently works perfectly with a trackpad (Mac/Safari), so please don't break that if you make changes for mouse users.

[lucsegers]

I would like to use the roadmap to know how long a project will take. For this I need to be able to set dependencies (2nd task can only be started when 1st task is finished, some can be done in parallel etc). Is there a way to generate these dependencies. Calculate start dates based on dependencies and calculate end date based on start date + expected time needed.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐