[Projects Beta] why is everything a draft?

[davetron5000]

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?

[kainino0x]

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.

[s-sajib]

+1 to this

[eporto2021]

+1

[macrogreg]

+1

[Jootiinha]

+1

[ApoorvaPasbola]

+1 , Would be better there was an option just like convert to issue to something like convert to a task which can have linked branch and MR for tracking 🤔

[Fil-SDSharp]

Sorry but adding an item and having it as a draft just does NOT make sense to me.
If 1% of the items are draft, then let me set those as Draft manually, but all others are Issues by Default.

At least let me choose MY default ADD (Draft | Issue)
So far, Draft is the most inconvenient thing in my initial usage of GitHub Project.
Every time i have to go thru the 2 steps process to CONVERT it !!

Also any reason why the workflow just relates to Status update?
Is there a way to set other fields that would make it more usable?
Will we have more than 2 boxes (When / Set) coming soon?

[Fil-SDSharp]

Love what i see so far, just don't understand that Draft (by default) inconvenience

[JLScribani]

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.

[vorcigernix]

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

[morgzz]

Seriously GitHub remove the verbiage Draft, maybe make it only appear when hovering over the card.

It is so cringy level distracting which is the main reason I was refusing to adopt and migrate my projects to the new version.
I find it so cringe that I'm using Ublock origin to remove it's existence. This was never forced in the previous versions of Projects.

Please allocate resources to update the UI and fix this.

[morgzz]

🙄, 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 DRAFT is so necessary in the UI?

[morgzz]

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.

[helgatheviking]

+1 Draft makes no sense to me. Plus a card may link to multiple issues.

[jarekwg]

Visual noise. Please hide it from the default view, so we can reclaim the vertical space.

[miguel-atenea]

+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.

[fedoteh]

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?

[PhABC]

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

[stephencawood]

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.

[BEEFF]

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!

[firmableharry]

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

[johnwargo]

yeah, that makes no sense at all

[vorcigernix]

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: ***@***.***>

[joryeugene]

Good recommendation. Thank you!

[iamWing]

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

[bharatsewani1993]

I tried the GitHub project for a week to manage my tasks!
But I don't like the Draft! most of my tasks are not directly related to any project repository:
For example, if I have to read something related to my work unrelated to the repository.

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.

[johnwargo]

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.
When I make a task on a board, I don't mind if it becomes an issue in the repo, but I want that to happen automatically and I want it closed automatically when I move it to done on the board.

That's simple MVP stuff.

[ToroNZ]

I can work around the "everything has to be an issue" but having to close things twice is so on brand.

[Energiz3r]

57th person here to say - I literally just saw GitHub projects were a thing, created my first one, and in under 30 seconds was looking for how to make an item not a Draft, only to end up here and find myself baffled and disappointed. What the actual f**k GitHub. At least respond!

[cquinteroj]

I also want to mention that in the draft issues, you can only add images, other file types such as PDFs or ZIPs cannot be added until the card is converted into issue.

We are moving from Jira to github to manage projects and have cards without the need to convert them into issues would be great.

[enzocomics]

I would also love to see a fix for this, please.

Edit: actually, never mind what I said. I started using projects as intended and I "get" it now. It's different from systems I've used in the past, so it took me some time to alter my expectations. Thanks

[Energiz3r]

you mean, you're creating an issue for every item to be actioned? out of interest, what's your project? I find for something that involves ideation and a 'to-do' list of possible future / out of scope features, it's really impractical to create issues for everything

[MuhammadRayyan16]

ok

[ghostinhershell]

Hi @Jetline007, we're happy you're here 😀

However, we currently do not allow job listings on the Community Discussions. It is something that we've added to the list to investigate, if we can do so without overwhelming other conversations. Keep checking back as the Community grows and we add more capabilities!

Thanks for your interest 👍

[Energiz3r]

Hi @Jetline007, we're happy you're here 😀

However, we currently do not allow job listings on the Community Discussions. It is something that we've added to the list to investigate, if we can do so without overwhelming other conversations. Keep checking back as the Community grows and we add more capabilities!

Thanks for your interest 👍

You've got time to comment on spam but not one minute to track down an update for this topic?

[BasalGanglia]

just adding my voice to the choir, please fix this

[lyyuta]

this is stupid, we are moving back to kanban

[josh-gree]

This is silly...

[adampaquette]

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. Tickets is probably a better name.

[JFWooten4]

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 Draft and mark an item as Completed with a green checkmark. I would also like the ability to remove the Assignees button. I don't want GH to delegate personal project items, only repo issues. More like a public personal calendar.

[abhibalani]

More than 2 year old issue. No response from the team. This is insane.

My bad, they did reply to a spam comment.

[alvesandreiolv]

So everything that is not an issue is a draft? Please remove this label.
I mostly got tasks in my projects, not issues.

[searls]

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

[justyn]

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.

[griessbreilp]

Is anything happening here? The "draft" is really confusing.
It adds nothing of value, and just makes it cloudy what it actually is.
You should add different kinds of objects with different input fields, but making everything a "draft" until you convert it into an issue is just... bad.

Please let someone with UI/UX Experience look over this. :/
(The tool itself is great, but just very confusing to use because of stuff like that. I hate that people dont understand that good software isn't having alot of features, but having few features that work really really great)

[azenMatt]

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

[searls]

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.

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

[justyn]

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.

[JFWooten4]

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 💜

[kingma-sbw]

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.)

[Sailsman63]

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.