Projects without Limits Private Beta

[queenofcorgis]

Thank you for your interest in helping us beta test the new Projects without Limits, which enables your project to have unlimited items. Our team is actively working to improve capabilities and incorporate your feedback.

Bugs and feedback

As this is still in private beta, bugs are expected and reporting of them is welcomed. If you notice any bugs, please drop a comment in the thread below. Screenshots/videos capturing the bug are appreciated. Our team will be triaging the thread and looking to address the bugs as soon as possible.

There are a couple of known bugs/feature gaps:

• As mentioned in the changelog, we currently support the table, board, and roadmap layouts. Features slice by, swimlanes, mobile, API, and insights are still in the works.
• There are some minor differences in filtering capabilities between existing Projects and projects with unlimited items. If you notice any that are affecting your daily workflow, please let us know below.
• We are actively working on latency and performance, and we have a couple of known bugs around live update irregularities.

Opting in

If your project is a good fit to join the private beta, project admins will see this waitlist banner. Click Join waitlist to be added to the beta waitlist. If space allows, your project will be flagged in.

Once you’re flagged in, you will see this banner on top of your project.

If you do not see the banner and would like to be added to the waitlist, please comment below with the following template:

Opt-in request

1. Are you the project admin? (Yes/No)
2. Link to the project to be added to the beta
3. Do you understand that not all features are supported yet? Your project will not have the ability to use slice by, swimlanes, mobile, API or insights during this private beta period. See changelog for reference.

Opting out

To reiterate, because this is still in private beta, bugs are to be expected. If you encounter bugs that are significantly deteriorating your daily workflow and you would like to opt out of the beta, please comment below with the following template:

Opt-out request

1. Are you the project admin? (Yes/No)
2. Link to the project to be flagged out
3. What part of the experience is causing you to opt out?

Our team will go through the list regularly to flag out these requests.

Please note that if your project has surpassed the 1.2k item limit and the project is then flagged out of Projects without Limits, then users will only be able to see the first 1.2k items of the project. To make the project usable again, you will need to archive items to get below the 1.2k limit again.

Note

As we perform maintenance from time to time, your project may be temporarily flagged out. If your project is flagged out for more than a couple of hours, please let us know here so we can remediate.

[DustyReagan]

It looks like -no:sprint might be broken in the Projects without Limits beta. no:sprint and -no:sprint are returning the same results.

[evi-liu]

Thanks for reporting, @DustyReagan! This is one of our known filtering bugs, and I'll circle back on this thread once this is fixed.

[ekroon]

I can confirm this happening on the https://github.com/orgs/github/projects/5842 project too.

[evi-liu]

@DustyReagan We just pushed out a fix for this bug! Can you confirm if -no: is working for you now?

[DustyReagan]

Looks to be working now! Thanks, @evi-liu!

[Shox2008]

response #1

[jwindmuller]

The assignee: filter is not showing options for all the people on the team like it used to:

[evi-liu]

@jwindmuller Could you try refreshing and seeing if you're still not seeing suggestions? We just pushed through something that should allow you to see suggestions again.

[jwindmuller]

@evi-liu thanks for letting me know, but it still doesn't show the list unfortunately, only 1 option for @me:

[evi-liu]

Got it - sorry about that. I'll have our team take a look at this. What's the link to your project?

[jwindmuller]

https://github.com/orgs/rpmsoftware/projects/14/views/1

[matthchr]

The banner seems to suggest the beta would be a good fit even for projects that aren't anywhere near 1200 items, see:

Current theory: It's not ignoring archived items? (or else archived items count against the limit, I thought they didn't though).

Example: https://github.com/orgs/Azure/projects/383

[kford-newrelic]

Yep, that seems to be the case for the banner itself but luckily, the board still works fine if you're above the 1200 (but below the 10k archived) limit

[evi-liu]

Good catch. We are including archived items as part of the "nearing 1,200 item limit" count, even though you are correct that archived items do not count against the limit.

We're looking to roll out a fix that only shows the banners for those nearing 1,200 active items. In the meantime, you can dismiss the banner if you don't feel like your project is in need of increased limits.

[oreininger]

It seems that the filter no:"tracked by" doesn't work anymore. When opening a tracked issue in the projet view, no connection to a parent issue is displayed:

But on the dedicated issue url, there is a connection:

[evi-liu]

The Tracks/Tracked by feature is currently in private beta, and as a result, it is not supported on Projects without Limits. There are no immediate plans to extend support for this feature.

Do you rely on that feature heavily? If so, I can opt your project out of Projects without Limits for the time being.

[oreininger]

Thank you for your quick answer! We do rely on it in our organization, so yes it'd be great if you can opt us out of the Projects without Limits beta!

Here is the link to our project: https://github.com/orgs/Feefty/projects/3
If needed, the admin is @marcantoine

[evi-liu]

Sounds good. Your project has now been opted out of the private beta, and you should be back on the previous experience.

[bczegeny]

@evi-liu The two projects you added of mine to the beta heavily rely on the tracked by grouping.
Looks like we will need to be opted out of the beta.

[rickpr]

Autocomplete for filters is not working - when I type assignee in the filter box it does not show completions. Milestones are also missing from completions. It also seems that a username with a - in it is not working for assignees (it's using the - as an OR presumably).

[evi-liu]

Thank you for reporting! The assignee bug is a known bug related to https://github.com/orgs/community/discussions/106785#discussioncomment-8447822.

As for the others, I'll have the team take a look into it. Thank you for helping us improve our product ✨!

[tnykodym]

For our project we also don't see proper list of Milestones in filters. It shows me just the oldest Milestone from each repo I have access to, nothing else. And even it doesn't complete anything when I start typing the name of one of the current Milestones.
Can you pls check that too? Thank you

[dmarcey]

Thanks @tnykodym - we're actively investigating here and hope to have a fix for you soon!

[darpank]

Hello, how can I check if my project has been accepted in the Beta? I am down to the last 49 issues and it would help to know if I should plan on archiving or not. Thanks!

[evi-liu]

Hi @darpank, if you're not seeing the opt-in beta banner and you would like to be added to the beta, please follow the instructions under "Opting in" found here.

[darpank]

@evi-liu - I had clicked in the banner to join the Beta about 10 days ago, after which that banner message disappeared which made sense. It was not clear to me how I would know whether I was still wait listed or accepted. Any chance you could let me know if I am still waitlisted, happy to follow the async process and paste an opt-in comment if you need me to but did not want to be redundant. Thanks so much for this feature and for the support during the beta on this thread!

[darpank]

@evi-liu Oh I see based on your responses to others, that a banner would indicate I am enrolled. Since I am not seeing that, will follow your instructions here, and thanks!

Opt-in request

1. Yes
2. https://github.com/orgs/trueanthem/projects/22
3. Yes

[evi-liu]

@darpank Your project has now been flagged in to the private beta! If you don't see the beta banner yet, give it a couple of minutes.

[darpank]

Thank you!

[hacky001]

slice by appears disabled for our project that is in this beta. It is enabled in all other projects that are not in this beta.

[dmarcey]

Thanks for reaching out @hacky001 - that is correct, there are a few features (like slice by, swimlanes, etc.) that aren't yet available in the beta. We've tried to call these out in the changelog post, and we'll let folks know as we bring these features back in the beta.

[dhythm]

Our current project is enrolled in the Projects without Limits beta this week.
Now, it looks sorting order crashed but it worked last week. 🤔

[dhythm]

Cannot select multiple items, so I cannot update/archive/delete items in bulk.

Beta

Not beta

[dhythm]

And I cannot copy iteration by dragging to another items for the bottom right blue square.

[dhythm]

Suggesting the label feature is gone. (before it was suggested like the following)

[evi-liu]

Thank you @dhythm for reporting these bugs and helping to improve our product. I've logged these as bugs for our team to take a look at and prioritize.

[dhythm]

@evi-liu Thanks for checking my report. I'm glad if beta Project will be more convenient!
It should help a lot of developers and teams!

[syxolk]

Our project appears to be completely empty as of yesterday evening:

https://github.com/orgs/Quintessence-Optimization/projects/92

What could be the reason?

[Phibedy]

@jayspadie thank you looks good :)

[jayspadie]

@Phibedy great! Thank you, and thanks for reporting the problem. We're reviewing our logs for any other projects that may have had problems with a recent re-sync, and we'll get those fixed soon too.

[jayspadie]

@ashnwade we've completed a re-sync of all projects, so yours should appear correct now too. Please take a look when you have a moment and let us know if you're still having problems. We'll continue to investigate the root cause. Apologies for the disruption, and thanks again for reporting the problem!

[syxolk]

The issue was been resolved as of yesterday evening (10 hours ago). Thanks for the quick reply and forwarding the problem, @jayspadie !

Of course, you would also need permission to view the referenced issues.

I definitely have and had permissions to view the issues of the repository.

I checked our telemetry and see that some number of items were archived on April 8

Yeah, we did not archive any issues directly before the incident.

If not, is this affecting others in your org who have access to that project?

Other people in my org were also affected. However, other projects (that we don't use that often) were not affected.

[ashnwade]

This issue was resolved. Thank you for the timely response.

[VeronicaPorubin]

We have this problem, don't work search for comment

[dmarcey]

Hi @VeronicaPorubin - sorry about that! Does it work if you put the sprint planning 42 portion in quotes?

So something like comm:"sprint planning 42" as the value in the filter?

[VeronicaPorubin]

Hello! @dmarcey still not working, and the same all of comments. Also the board works very slowly!!

[VeronicaPorubin]

sprint just is value in the filter, not all context or other words

[synth]

Bug report:

In board view, the columns don't load all the items into the view. Only a small number of items initially load and a placeholder item is left. We have to shrink or modify the view so the placeholder item is scrolled out of view and then scroll it into view so the remaining items are asynchronously loaded. This bug has been present for the last few weeks, maybe more. We have to shrink our window around every time we want to view the project which is obviously a pain. Hoping this can get fixed soon.

[dmarcey]

Thanks for the report @synth - we'll take a look here and try to get a repro. Do you mind sharing the project URL where you're encountering this? If you don't want to share it publicly, feel free to email it to me at dmarcey AT github.com.

Also, just to confirm, this happens every time you load the board view, it's not intermittent, right?

[synth]

Correct, every time. I will email you the project url. Thanks!

[dmarcey]

Thanks again for reaching out @synth. We believe that the bug had to do with handling a very "wide" board with many columns. We just shipped a fix this morning which I think should address this issue - let us know if it is resolved for you! Thanks for your patience!

[tohyongcheng]

Hi @evi-liu, please help activate us for the private beta:

Are you the project admin? Yes
Link to the project to be added to the beta https://github.com/orgs/xendit/projects/7/
Do you understand that not all features are supported yet? Yes

[evi-liu]

Your project has now been added to the beta! Let us know if you have any feedback or questions.

[iampremo]

Bug:

Our public project has issues within it from both public and private repos.

We have had users let us know that they can sometimes see the titles for some of the private issues that are in the project, in the screenshot below issue 23 is in a private repo.

When they attempt to open the issue they are correctly taken to the 404 page.

[iampremo]

maybe related, sometimes the private items are not visible at all, sometime they show up as "You can't see this item".

[jayspadie]

We have a temporary regression that's falling back to showing placeholder "You can't see this item" for items to which the user does not have access, similar to the previous product behavior before Projects Without Limits. We'll get a fix out soon to again prevent them from showing at all again. Thanks for reporting.

[jayspadie]

@iampremo, we've deployed a fix for redactions now. You should no longer see placeholder "You can't see this item" in projects enabled for Projects without Limits.

You also originally noted that issue titles from a private repository were visible in a public project. This should never be the case, and should not have occurred with the recent regression given our fallback redactions that replace the item with "You can't see this item".

Would you please verify that things are working correctly now for you, and reply in this thread? Also, if you still believe it is showing private issue titles in a public project, would you mind emailing the project URL to me directly so I can take a look? The address is my GitHub handle at github.com. Thanks again!

[iampremo]

Hi @jayspadie looks like all the issues here are now resolved and our users haven't been able to replicate the private issues been seen :)

Our project is public so if you are interested then please feel to have a look https://github.com/orgs/YoYoGames/projects/17/views/24

[jayspadie]

Thanks for confirming all's good now, @iampremo!

[ben-gryps]

Bug:
I am trying to filter a project board by assignee and no filter is applied to the issues. I commonly use assignee:@me. This is not working. assignee:user also does nothing to filter issues. I noticed this in my project board around 4/3/24.

[jayspadie]

Hi @ben-gryps. Sorry to hear you're having problems. Does filtering on other fields work for you, or is it only on assignees? Also, does attempting to filter on assignees return no items, or lots of items (with assignees other than the filter value)? Lastly, if you filter only on assignees, does it appear color coded like this?

[jayspadie]

Ah, I notice you have a hyphen in your GitHub handle. I believe we have have an known bug with it matching ben or gryps. Are there any non-hyphenated assignee values you could try to confirm if that's the problem?

[jayspadie]

...Conversation continued in the next discussion item.

[jayspadie]

FYI, we've just deployed a fix for this. You should now get only exact matches when filtering on assignees, even for those with hyphenated usernames.

[ben-gryps]

I typically use ***@***.***` and that is not working. Also adding quotes around my handle does not work. My workaround right now is to type my handle as a text filter

…

On Thu, Apr 18, 2024 at 9:20 AM Jay Spadie ***@***.***> wrote: Ah, I notice you have a hyphen in your GitHub handle. I believe we have have an known bug with it matching ben or gryps. Are there any non-hyphenated assignee values you could try to confirm if that's the problem? — Reply to this email directly, view it on GitHub <#106785 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZVZYY5Z7I6EOB5YECEFFWDY57QEDAVCNFSM6AAAAABC72KQJ2VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TCNJWGQ2TO> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[jayspadie]

Thanks for your reply and yes, I checked and we do have a bug on our backlog to address this problem with hyphenated handles. And as you noted, full text filtering is the closest thing to a workaround for now. Sorry about that. Hopefully we'll get it fixed soon.

[ben-gryps]

Thank you. My apologies for creating a new thread

…

On Thu, Apr 18, 2024 at 9:32 AM Jay Spadie ***@***.***> wrote: ...Conversation continued in the next discussion item <#106785 (comment)> . — Reply to this email directly, view it on GitHub <#106785 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZVZYYZKXXTZ2KM34IDNI5TY57RSFAVCNFSM6AAAAABC72KQJ2VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TCNJWGYZTA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[darpank]

I see a performance issue I wanted to document.

A view of our project lists all the issues we have fixed, grouped by milestone, sorted descending by milestone. This used to load instantaneously prior to joining the Beta. I timed it today and it took 16 seconds to load.

I am hoping that this can be fixed, or at least worked around by the introduction of pagination maybe? If you want to see this in action it is view number 4 in our project, alternately I can email a video recording. Thanks!

[jayspadie]

Hi @darpank. I believe Evi is unavailable for just a bit, so if you'd care to send that video to me too, I'll make sure it gets included in an issue for investigation. You also noted some weird loading behavior in one of your views below. If you have any other information on that, including the URL to the project, please send that to me too. My email is my GitHub username at github.com. Thanks!

[darpank]

@jayspadie forwarded the video to you, thank you! I will follow up on the second issue in its thread below.

[jayspadie]

@darpank got it! Thanks. After watching the video, I realized that this is a known bug (one that I filed myself earlier this year, coincidentally). Basically, we're not fetching groups in descending order as we should for cases like this. Instead, we're fetching groups in ascending order, and we're falling back to client-side code that renders them correctly in descending order. This works fine with just a few groups, but in your case with many milestones, we're triggering pagination for additional groups several times until they've all been fetched and rendered. This causes that stuttering effect you're seeing. I'll bump up the priority of this issue and hopefully get a fix out sooner.

In the meantime, if you want to avoid the slow, stuttered load for that view, you may want to consider options such as:

• Show the milestone field in the table and continue to sort descending, but remove the milestone grouping
• Filter the view(s) for milestone years to reduce the number of groups per view (You should be able to filter on milestone:2024* for example)

Thanks again for reporting the issue. I think we should be able to fix it within the next couple of weeks.

[darpank]

Awesome @jayspadie and thank you for your help.

[darpank]

The milestone:2024* works well too btw.

[sbschorer]

Bug: When I try to archive all elements in a column (screenshot) only the first 15 items get archived.

[sbschorer]

It seems to work, when there are <100 Items in the column.

[jayspadie]

Thanks for your feedback, @sbschorer. Yeah, this is a known limitation for now. Currently, we only perform bulk archive and delete on items that are actually loaded on the client. You can work around it by scrolling to load more for a particular group/column, and you should see that message "archive X items?" increase when more are loaded. We plan to improve this in the future.

[darpank]

For one of our views (number 39), custom fields do not render the first time that view is opened in a browser tab. A refresh fixes it.

[darpank]

I am seeing a few other things, noting them here in case that helps:

1. At times some rows have the right values.
2. Any cells that have the values tend to be at the bottom.
3. Even where there are values, a row may have one or more of the custom fields not rendered - i.e. it is not all or nothing at the row level

[jayspadie]

Interesting. Thanks for reporting. Please see my comment above about sending additional information to help us investigate. Thanks again.

[darpank]

• The project is https://github.com/orgs/trueanthem/projects/22.
• This behavior is only seen with custom fields I have added, standard fields like Title, Labels, etc always load just fine.
• I can make this happen consistently by opening the view in a new browser tab. A refresh solves the problem and then clicking out of that view and coming back does not create the issue.
• It is not all or none for a given row i.e. in a given row some custom fields will load and some might not
• If any get loaded, they tend to be clustered at the bottom

[jayspadie]

Thanks for the additional info, @darpank. Not sure what's going on here yet, but we'll continue to investigate.

[stoutgz]

I hope I'm not wasting your time too much by commenting here, but I just want to say that I'm excited for this feature as I have a project board that is consistently running into the 1200 item limit. 1200 has actually been a decent number to keep me in check and make sure I have some good archival/deletion/housekeeping practices, but still being able to go beyond the 1200 will be very welcome as I worry I may lose track of items that don't get automatically added when I am running into the limit.

While I'm not willing to make the sacrifice for the known trade-offs of the beta at this time, I just wanted to share that I am thrilled to see the active development and focus on the feature and am inspired by the activity that I see on this forum. It's looking like a successful way to run a beta 👍👍.

Cheers to you Github devs 🍻! And thanks for doing your part too, beta testers 🎉!

[ashnwade]

I was enrolled in the beta and did not ask to be removed, but it looks like I am no longer in the beta and I am missing issues from my project board.

In particular:

• I no longer see the link to Beta Feedback at the top of my project
• The group by and slice by features that were disabled in the Beta are enabled again
• I am missing about 150 issues, presumably because I was over the 1200 limit that was previously enforced.

Can my beta access and missing issues be restored?

[ashnwade]

This is fixed. Thanks!

[jayspadie]

Apologies for the disruption and fear of losing newly added issues, @ashnwade! We had to briefly disable Projects without Limits features for a few minutes to make some index updates. During this time, projects revert back to showing only the first 1200 active items. Once completed, everything returns and no information is lost. We're working on making these updates transparent to our end users, but we're not there yet. Thanks for reporting, and apologies again for the unsettling experience.

[dagguh]

Hello @evi-liu, we'd like to join the beta:

Are you the project admin? Yes
Link to the project to be added to the beta https://github.com/users/SaintVigeous/projects/1
Do you understand that not all features are supported yet? Yes

[dmarcey]

Your project has now been added to the beta! Let us know if you have any feedback or questions.

[ekatek]

Hi! We would like to join the beta.

Are you the project admin? YES
Link to the project to be added to the beta: https://github.com/orgs/token-transit/projects/1
Do you understand that not all features are supported yet? Yes.