[Projects Beta] why is everything a draft? #10317
Replies: 79 comments 71 replies
-
|
A draft issue is one that has not been filed as an actual Issue on a repository. Use the "Convert to issue" button (in the left-side down-arrow menu on the row or draft issue pop-over editor) or set the draft issue's "Repository" field to auto-file the issue into a repository. |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
+1 , Would be better there was an option just like |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
Sorry but adding an item and having it as a draft just does NOT make sense to me. At least let me choose MY default ADD (Draft | Issue) Also any reason why the workflow just relates to Status update? |
Beta Was this translation helpful? Give feedback.
-
|
Love what i see so far, just don't understand that Draft (by default) inconvenience |
Beta Was this translation helpful? Give feedback.
-
|
Agree. This is why I've abandoned my project for task management. There are too many steps to add an item, and it creates a poor user experience. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah. I have tasks like "create social" - draft state by default does not make sense. It is good to know what is code related issue, but marking everything else a draft id simply a bad UX |
Beta Was this translation helpful? Give feedback.
-
|
Seriously GitHub remove the verbiage It is so cringy level distracting which is the main reason I was refusing to adopt and migrate my projects to the new version. Please allocate resources to update the UI and fix this. |
Beta Was this translation helpful? Give feedback.
-
|
🙄, Still here as of 4/30/2023. The new user menu is nice, but I'd rather someone remove the verbiage. Seriously, whichever product manager is responsible for this feature, could you perhaps shed some reasoning why this verbiage |
Beta Was this translation helpful? Give feedback.
This comment was marked as spam.
This comment was marked as spam.
-
|
Update... it's 2024 and GitHub now forcing everyone to the new Project 😒. I've migrated and everything is labeled a f****ing [ Draft ] 😌 Hate the new UI, won't be using GitHub projects. Rest in Peace Project Classic. |
Beta Was this translation helpful? Give feedback.
-
|
+1 Draft makes no sense to me. Plus a card may link to multiple issues. |
Beta Was this translation helpful? Give feedback.
-
|
Visual noise. Please hide it from the default view, so we can reclaim the vertical space. |
Beta Was this translation helpful? Give feedback.
-
|
+1 On removing the draft label thing and maybe create something else that's able to be linked! As other mentioned before, a card may link to multiple issues. |
Beta Was this translation helpful? Give feedback.
-
|
It's been a year with this thing already, are there really any plans to include something different besides Draft and Issues as labels? Why don't we have tasks? |
Beta Was this translation helpful? Give feedback.
-
|
Any update please? IT's a huge blocker, especially since draft don't show up in the filtered view since they don't inherit filter's label |
Beta Was this translation helpful? Give feedback.
-
|
I agree with the others who don't want Draft to be the default. I want a new item to be automatically created as an issue under a project I have selected. Like others have pointed out, almost everything I create has to be converted to an issue and added to the project manually. It's a waste of time. |
Beta Was this translation helpful? Give feedback.
-
|
I guess if this was a business choice you would want all users to convert all items to issuers it could improve GitHubs S.E.O. But this is a community platform, we want answers! |
Beta Was this translation helpful? Give feedback.
-
|
It confused me like anything, and I was trying to find the CTA to change that to active or something else, but the only way I can fix it is by converting it into an issue. Why does every TODO item need to be an issue? INSANE |
Beta Was this translation helpful? Give feedback.
-
|
yeah, that makes no sense at all |
Beta Was this translation helpful? Give feedback.
-
|
Unsubscribing, moved to Linear. GL.
…On Sun, Mar 5, 2023, 2:26 PM John M. Wargo ***@***.***> wrote:
yeah, that makes no sense at all
—
Reply to this email directly, view it on GitHub
<#10317 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABLZOEY375Q7LT3FFQNM2DW2SIANANCNFSM5MLAWEPA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Good recommendation. Thank you! |
Beta Was this translation helpful? Give feedback.
-
|
While I don't mind having the item created as draft by default, I'd definitely love to be able to create project-wide templates and able to choose the template to apply when drafting an issue. Also need to be able to reference other issues when it's still a draft |
Beta Was this translation helpful? Give feedback.
-
|
I tried the GitHub project for a week to manage my tasks! After a week I decided to move away from the Github Project because it shows each and every issue as a draft if it is not related to the repo. |
Beta Was this translation helpful? Give feedback.
-
|
Not only does this make sense, but when you have a item linked to an issue and you move it to completed, it doesn't close the issue. This feature used to be a great, simple way to manage tasks - now it's useless. I expect projects to be part of the repo, not global. That's simple MVP stuff. |
Beta Was this translation helpful? Give feedback.
-
|
I can work around the "everything has to be an issue" but having to close things twice is so on brand. |
Beta Was this translation helpful? Give feedback.
-
|
This is silly... |
Beta Was this translation helpful? Give feedback.
-
|
I have a series of tasks to plan for my project and I was wondering why everything is a Draft, how can I remove this label. I saw the option to convert to an issue but it made no sense because this is not a problem, this is a work item. I lost time seaching and I just now realised that projects with 400 issues are not probably not full of bugs, this is just misleading. |
Beta Was this translation helpful? Give feedback.
-
|
I am using Projects for a similar scope so that I can document things I'm working on and mark them as "Archived" when finished, but this looks weird when completed items are still a "Draft."
I would like the ability to click |
Beta Was this translation helpful? Give feedback.
-
|
More than 2 year old issue. No response from the team. This is insane. My bad, they did reply to a spam comment. |
Beta Was this translation helpful? Give feedback.
-
|
My guess they are too busy pushing mostly useless AI wherever they can 😏 |
Beta Was this translation helpful? Give feedback.
-
|
So everything that is not an issue is a draft? Please remove this label. |
Beta Was this translation helpful? Give feedback.
-
|
Hate for this to be a pile-on, but it really feels to me like adding a couple settings: (1) default repository and (2) auto-create issues would make Projects much more useful to small, low-ceremony teams. As it is, if my product owner makes a bunch of draft issues and reprioritizes them, I won't receive any notifications unless they also figure out how to (and understand why they need to) convert them to issues |
Beta Was this translation helpful? Give feedback.
-
|
If issues were able to be associated with the Project itself, rather than a specific repository, created issues (or drafts) could automatically associate with this unless another repository was selected. Behind the scenes this would basically be an "invisible" issues-only repo created and associated with the Project. |
Beta Was this translation helpful? Give feedback.
-
|
Is anything happening here? The "draft" is really confusing. Please let someone with UI/UX Experience look over this. :/ |
Beta Was this translation helpful? Give feedback.
-
|
This remains on our list to address but we are still a few months at least off from being able to do so. The first step we want to make here is to reduce the reliance on 'drafts' as the default and make it easier to go straight to an issue. The question on an issue needing to have a repository is a much bigger architectural problem for us to address but something we are also looking into for the long term. I will share more on some of the initial steps here when we have more details |
Beta Was this translation helpful? Give feedback.
-
One has to imagine this would be an absolutely massive lift to pull off relative to the primary pressure point being hit on in this discussion. Even if the short-term solution was to have an optional configuration to set the default repo association to a project (since, for small and medium teams, project:repo is very often 1:1), that'd be a huge boon to basic UX in Projects |
Beta Was this translation helpful? Give feedback.
-
|
Whilst I think @searls suggestion makes sense, I don't necessarily agree that the assumption should be that the standard approach to project:repo is 1:1. But I don't argue against setting a default project in Projects, just suggest making sure the UX elsewhere can easily deal with Issues across different repos. For example, an Epic may contain Tasks from another repo (in the "Issue Types" scenario). @azenMatt has previously suggested that a recommended approach (used internally in Github) is to use a dedicated issues-only repository for planning. This would be a good candidate to be "default" for any project used across multiple repos. The great thing about using the "default" repository idea for the "planning" repo (of course, only for multi-repo projects) is that this should entirely emulate the longer-term desired feature of Project-only issues, with the sole exception that the planning (aka Project-only) repo is visible. This approach would be immediately useful for many, would allow the UX to evolve to accommodate this use case and therefore would be a smooth UX transition to real Project-only issues once the backend architecture can support issues without a repo. |
Beta Was this translation helpful? Give feedback.
-
|
Agreed, we do not have nearly as many Projects as repos. Forcing new items into any new repo for tracking would seem duplicative and redundant. Tank your time 💜 |
Beta Was this translation helpful? Give feedback.
-
|
This would require a repo for each project? that won't make sense for Projects that don't have repos for instance where versioning in git won't be possible (WordPress Pagebuilders, Database Projects, graphic desgin projects. etc.) |
Beta Was this translation helpful? Give feedback.
-
|
No, you can have projects tied to the org level (or your personal user account for that matter) The issue is that individual entries are stuck in this "draft" status until they are assigned as an issue on a specific repository. Some of us find this too limiting even when everything really is source code in git. |
Beta Was this translation helpful? Give feedback.
-
|
Still not resolved, it is almost 2025. You don't need to be some UI genius to see that this "Draft" label just clutters the valuable space in the columns. At least let us rename this field to something less confusing. |
Beta Was this translation helpful? Give feedback.
-
|
Yes. renaming too " " would be preferred. |
Beta Was this translation helpful? Give feedback.
-
|
2025 has come. The Draft is still there :( |
Beta Was this translation helpful? Give feedback.
-
|
I added a custom ad-block filter for them, so now my UI looks clean. This feature has negative value for me, and I just spent 1 hour trying to figure out how to remove it. |
Beta Was this translation helpful? Give feedback.
-
|
I got used to pressing the + button to add an item and then CTRL + ENTER to create an issue directly ... that works fine ... it's cumbersome, since I would like to be able to set this in settings as my default, but hey I guess we're not paying enough to make this happen ... |
Beta Was this translation helpful? Give feedback.
-
|
If you type |
Beta Was this translation helpful? Give feedback.
-
|
please simplify or eliminate drafts! 👍🏼 |
Beta Was this translation helpful? Give feedback.
-
|
Is it also not possible to bulk update and convert all to issue at the same time? |
Beta Was this translation helpful? Give feedback.
-
|
2025, still draft label is here |
Beta Was this translation helpful? Give feedback.
-
Just created a new projects with projects beta and every single thing I created has a dotted circle and a gray "Draft" label that I cannot remove or change. What is this intended to be for and can it be removed?
Beta Was this translation helpful? Give feedback.
All reactions