if someone from github is looking at this, can u please include Gitlab's "Scoped Labels" in this - <a href="https://docs.gitlab.com/ee/user/project/labels.html#scoped-labels" rel="nofollow">https://docs.gitlab.com/ee/user/project/labels.html#scoped-l...</a><p>it seems that the new issues are going to operate on the basis of labels (as it should). Scoped/Nested labels are a godsend. For example, I can tag an issue with a label "UI::App::Android" and i should be able to filter on the basis of "UI::App" and get all issues.<p>One of the things i still notice about the boards is that it is created on the basis of status. Gitlab's boards are created on milestones/status...or LABELS. <a href="https://docs.gitlab.com/ee/user/project/issue_board.html#organization-of-topics" rel="nofollow">https://docs.gitlab.com/ee/user/project/issue_board.html#org...</a><p>Most importantly, dragging tickets across boards will change the labels. This is far more powerful than just hardcoding them on statuses.
It floors me that they haven't addressed the underlying architecture issues that made Issues unusable: Issues are only for a single repo. Business users don't (and shouldn't) know what repo to add an Issue to. This is why we moved away from Issues and none of these new visualizations make the product usable until they deliver multi-repo issues.
In case the GitHub Issues team is still looking here, I have a request! Can you put the name of the commenter somewhere besides just the name field in the email from? Currently it's something like, Poster Name <notifications.github.com>, but that means you can't tell who the poster was from the email content itself.<p>I use Apple Mail and have a contact for GitHub since that provides benefits like an avatar, easier search, etc, but now the contact clobbers the name field and I just see every email from "GitHub" with zero indication who wrote the comment.
"it's just a spreadsheet, and [view X] is a filter on that sheet" is a nice mental model. I've had <i>lots</i> of managers organize stuff in google sheets and then copy to [task manager X] simply because it's easier to think about - they'd probably love this. I certainly would, vs Jira's massive "everything is custom UI / a unique concept" mess.
> Bored of boards? Switch to tables.<p>I love this. I don’t know why the “agile board” became a thing. To me it always seemed like a poor way to visualize what is a list of items.<p>My problem with agile boards is that they place tasks into separate columns to denote the task state, which often cuts off the task description (and can require a lot of horizontal scrolling). It also prevents using columns for other fields like the Assignee (as the table view in the new GitHub Issues does).
The UI, down to the content and styling of menus, looks a lot like Linear. I'm chuffed to see the best parts being borrowed, but it looks like they've made sub-tasks/issues too simple, as they aren't first-class issues, but mere checkboxes with short descriptions.<p><a href="https://linear.app" rel="nofollow">https://linear.app</a>
There is currently a move to disable issues (in opensource projects) and the driving factor behind this, is that other people can basically put stuff on your todo-list.<p>What would be better:<p>- make issues read-only for non-members<p>- track problems in discussions. often they're not really bugs and other people can directly help. If not, I'll convert the discussion to an issue when appropriate.<p>Benefit: bugs as discussions can be upvoted or downvoted so the community helps prioritizing.
I am longing for the day they deprecate Azure Devops and merge it into GitHub Enterprise.<p>This is the only way I’ll ever get the ability to work with GitHub in my company, which has a much superior UI/UX imo.
I'm more interested in GitHub's Issue Forms (as an evolution of Issue Templates): <a href="https://twitter.com/frenck/status/1355620350176976901" rel="nofollow">https://twitter.com/frenck/status/1355620350176976901</a><p>Does anyone know what the status of these is?
I wonder how tense things are over at Atlassian right now. Jira seems so universally hated that it feels like any competition that ticks a few basic needs could start hurting them.
Wow, there's a lot of Airtable in here. My team used GitHub Issues/Projects for a while, but ultimately moved to a custom Airtable solution for project management, release management, etc which gave us the tables, views, filters, groups, you name it. Seems like someone at GitHub got the notice about users wanting that more flexible UI/UX. Good on them!
This looks like a great step forward.<p>I always found it interesting that proposed enhancements are thrown into Issues. Maybe it's the word "issues" itself because I associate it with a negative connotation.
Github should first fix that it displays "issues" of a repository instead of useful info when exploring <a href="https://github.com/explore" rel="nofollow">https://github.com/explore</a><p>Why would I want to see issues of a repo I have no clue about? I am there just to discover a new repo.
As a PM who recently moved our eng team from Jira to GitHub (it was a good move btw), this is amazing news! It solves so many of the little problems that GitHub issue caused us, really looking forward to using it!
related blog post: <a href="https://github.blog/2021-06-23-introducing-new-github-issues/" rel="nofollow">https://github.blog/2021-06-23-introducing-new-github-issues...</a>
This doesn't seem to have the one feature I want most, which is the ability to track the status of projects and milestones that span multiple repositories. Anyone know if this is there and they didn't mention it, or is on the roadmap?
If anyone from Github is here, can you please allow attachments of unrecognized file types? You won't let users attach their binary .plist prefs files and this makes Github issues unusable for my project.
Nice.<p>Github has all the incentives and infrastructure in place to build all the layers on top of the repositories and existing social network. Ive seen a bunch of companies launch with competing project boards, ci systems, etc but its not clear how you carve out a space for yourself from within a set of reasonable defaults.
> Automatically add issues to a project,<p>That was the one thing I actually absolutely needed missing from current "Projects". Seems like such a simple basic thing, but the fact that I couldn't make it so a new issue created automatically showed up on a project board was a stopper for me.
Question: how does the Table view headings reconcile to the Board view?<p>On the Table view, there is a heading for: "Prototype", "Beta" and "Launch"<p><a href="https://github.githubassets.com/images/modules/site/planning-tracking/layout-table.png" rel="nofollow">https://github.githubassets.com/images/modules/site/planning...</a><p>But when you look at the Board view, I don't see "Prototype", "Beta" or "Launch" denoted anywhere on the card.<p><a href="https://github.githubassets.com/images/modules/site/planning-tracking/layout-board.png" rel="nofollow">https://github.githubassets.com/images/modules/site/planning...</a>
So for a non-developer that wishes to collaborate, they now need a GitHub license? That's a deal-breaker right there for any org that is composed of more than developers.
Airtable is the most amazing thing that has happened to UI in years and it's really nice to see their ideas crawling on to other contexts like GitHub here.
Is there any info on how this would help with estimation and planning of a large number of tasks. E.g. "what can we get done this quarter?"<p>I have an eye on <a href="https://www.openproject.org/" rel="nofollow">https://www.openproject.org/</a> because it seems to have these sort of features. I currently use Excel for this.
Really looking forward to the boards & ability to split check boxes out into new tasks. Being able to decompose business issues into workable technical items has always been a challenge for us. The impedance of needing to create a new issue and copy stuff over from the big one would encourage us to not always do this.
Oh me and everyone I know have been waiting for this.<p>Why use any other Issue tracker if Github can do this itself? Countless integrations would be replaced by this. I wonder what would happen to all those dashboard / issue tracker / project tracking apps now.
I've mixed feelings.<p>On one side, I like seeing something different to the crap that is Jira. Every single large company out there seems to use it and it's terrible.<p>OTOH, not sure if I'm happy that the only new competition is a Microsoft product.
I don't use GitHub Issues [much] because I was under the impression that issues are not themselves stored as a git repo, but rather they are some kind of proprietary database GitHub maintains. Thus they create lockin for GitHub.<p>Am I wrong about this?
I'd like to be able to run reporting out of this so I can gather velocity metrics (for my boss) at the developer/project/milestone/arbitrary label level. It doesn't look like there are too options for this yet.
they built notion boards into github. nice work! we've been using notion for our product work and it's been very flexible and powerful, but I do miss having the code and issues living together.
I can't tell if they've handled it here, but one of the things I'd love to see is a "friendly" view into issues for non-coders. In my experience, when a non-coder sees something that "looks like code" they become confused and frightened and generally avoid the interface.
Omg, they did a copy of Asana.
And not a copy of the good part, but a copy of the useless unergonomic eye candy parts ...<p>And I hate so much Asana... It is so inefficient and frustrating to use.<p>So, please, fire the designer that proposed this change before it can become mainstream.<p>I don't understand the hype about the "board" thing. I guess that people think that they look cool and doing agile by using a board.<p>But compare that to a normal table that you can reorder by columns based on your wishes...