Issue Types Private Beta: Feedback wanted!

[rileybroughten]

Thank you for participating in the Issue Types private beta which comes alongside the brand new Issues experience ✨ Please leave your feedback below on what is working well, any bugs you encounter, and what else you’d like to see!

You can also visit discussions on the new issues experience and sub-issues to provide your feedback on those experiences.

Issue types

Issues types allow you to classify and manage your issues with a shared and consistent language across repositories in the organization, such as bugs or tasks.

Customizing default issue types

An organization administrator can customize the issue types for the organization from the organization settings "Planning" page in the “Issue types” section. These are available for all repositories in the organization by default.

Organization settings page

Adding a type to an issue

When you create a new issue, you can change the type using the dropdown to the right of the filter bar.

Screen.Recording.2024-03-16.at.1.05.12.PM.mov

Additionally, you can specify the type qualifier in issue forms in your repositories, so that each issue created from each template automatically has the type set.

Issue form with `type` field

If you’d like to add or change the issue type for existing issues, you can update it from the repository page by selecting one or multiple issues using the checkbox to the left of each issue, or from a project using the Type field by copying and pasting or dragging cells.

Creating custom views in your project

In a project, you can use the new Type field to customize your views by filtering, sorting, slicing, or grouping, so you can visualize your issues.

You can even use the Type field in the auto-add to project workflow, so you can automatically add these to your project.

Auto-add to project workflow

Automating issue types

There are now typed and untyped webhook payload objects for the issues webhook event that trigger a GitHub action.

For the GraphQL API, there is an IssueType object to manage issue types at the organization level to create, update, and delete them. You can also create a new issue with an issue type, update the issue type, and query a repository by issue type.

Click to view GraphQL details

Note that these requests will need to include the GraphQL-Features header with a value of issue_types.

Objects and Fields

Query Issue.IssueType
Returns issue type based on issue ID

  node(id:ID) {
    ... on Issue {
      issueType {
        id
        name
      }
    }
  }
}

Query IssueType
Returns fields for issue type i.e. private, enabled etc.

  node(id:ID) {
    ... on IssueType {
      id
      name
      isEnabled
      isPrivate
    }
  }
}

Query IssueType.issues connection (w/ repository argument)
Returns total count of issues (with associated fields i.e. title, state etc) with an issue type based on specified repo.

  organization(login: LOGIN) {
   issueTypes(first: 10) {
      nodes {
        id
        name
        # Fetch the first 10 issues with this issue type
        # From the given repository
        # With an open state
        issues(first: 10, repositoryId: REPO_ID, states: OPEN) {
          nodes {
            id
            number
            title
          }
          totalCount
        }
      }
    }
  }
}

Query issueTypes using global search filter API
Org wide searches for issue type.

  search(type: ISSUE, first: 100, query: "type:Bug org:production") {
    issueCount
    nodes {
      ... on Issue {
        title
        repository {
          nameWithOwner
        }
      }
    }
  }
}

Mutations

Create Issue Type

mutation {
  createIssueType(input:{
    ownerId: "ID"
    name: "NAME"
    isEnabled:true
    isPrivate: true
  }) {
    issueType {
      id
    }
  }
}

Update Issue Type

mutation {
  updateIssueType(input:{
    issueTypeId: "ID"
    name: "NEW NAME"
  }) {
    issueType {
      id
    }
  }
}

Delete Issue Type

mutation {
  deleteIssueType(input:{
    issueTypeId: "ID"
  }) {
    deletedIssueTypeId
  }
}

Create Issue -> w/ Issue Type

mutation {
  createIssue(input: {
    repositoryId: "ID"
    title:"test-api-2"
    issueTypeId: "ID"
  }) {
    issue {
      id
      url
    }
  }
}

Update Issue -> w/ Issue Type

mutation {
  updateIssue(input: {
    id: "ID"
    issueTypeId: "ID"
  }) {
    issue {
      id
      url
    }
  }
}

Update Issue Issue Type

mutation {
  updateIssueIssueType(input: {
    issueId: "ID"
    issueTypeId: "ID"
  }) {
    issue {
      id
      url
    }
  }
}

Next steps

We are continuing to improve the Issues experience, and so we’d love to hear your feedback as you try out the new experience and start using issue types.

Note: You can opt out of this experience, which will bring you back to the current experience and remove your access to issue types.

[seymourisdead]

this looks awesome! Is it possible to enroll to private beta for this?

[garrettm]

Seconded, looks great and I'm also interested in the beta!

[MarkOSullivan94]

I'm also keen to get involved in testing

[rileybroughten]

We're expanding this private beta so let me know the name of your organizations so we can get you flagged in. Thank you!

[andreakmich]

Our organization (tesseracthealth) would love to get flagged in for the private beta!

[rileybroughten]

@andreakmich see this comment below for gaining access!

[mshish]

Would love the opportunity to join the private beta and provide feedback. About to build out a backlog from scratch and would like to avoid using a third-party integration to make it manageable.

[rileybroughten]

Thank you for your interest! We are still enabling the new experience and issue types for a limited number of organizations at this point, but we will post an update here once we are ready to roll this out to a broader audience and gather more feedback! 👍

[rileybroughten]

@mshish what is the name of your organization?

[kalanchan]

hello! I'd like to participate in the beta, and trying out the new issues experience! We were looking into moving our github issues over to a different platform as it lacked the ability to track cross repository dependencies, but this seems like a great start to meeting our needs.

[rileybroughten]

Thank you for your interest! We are still enabling the new experience and issue types for a limited number of organizations at this point, but we will post an update here once we are ready to roll this out to a broader audience and gather more feedback! 👍

[rileybroughten]

@kalanchan what is the name of your organization?

[esmarkowski]

This looks great! Would love to participate in the beta.

[rileybroughten]

We are still enabling the new experience and issue types for a limited number of organizations at this point, but we will post an update here once we are ready to roll this out to a broader audience and gather more feedback! 👍

[rileybroughten]

@esmarkowski what is the name of your organization?

[some-natalie]

Hey @rileybroughten , overall I ✨ love ✨ it!!

However, I find myself toggling it off to bulk unassign users from issues. It'll let me assign myself in bulk, but not remove myself.

[rileybroughten]

@some-natalie thank you for the feedback! I wasn't able to reproduce this when making bulk edits from the repository listing page to assign and then unassign myself, so if you're able to provide a video that would be helpful!

[KevinRaney]

Can I be added to the Private beta please? I can test with a few orgs.

[rileybroughten]

Thank you for your interest in participating! We are enabling the new experience and issue types for a limited number of organizations at this point, but we will post an update here once we are ready to roll this out to a broader audience and gather more feedback! 👍

[rileybroughten]

@KevinRaney what is the name of you organization?

[KevinRaney]

@rileybroughten we have 2 @RaneyDomain & @PWCIT

[rileybroughten]

These have been added!

[akasey123]

Hi,
I am unable to get the Projects gear to populate any tags for status which means that I can't move renewal issues forward to the next stages. I have attached a screenshot of this bug/issue.

[mariaKatz]

Hello,
i've tried the "Issue Types" - nice experience - easy to create and to use. I'm missing the ability to define the hierarchy between types.

[rileybroughten]

Thank you for your feedback @mariaKatz! Could you share some more details on how this would ideally work for your organization and how you'd expect this to work? For example, what is the ideal issue type hierarchy you'd want defined or recommended for your organization?

[mariaKatz]

Hi, Thank you so much for quick response on my suggestion. From my point of view at least we need to be able to define the parent-child relationship between Issue Types: * it means once new type is created, I can define the relation :parent of/child of (or contains/contained or any other name that you that will better define the relation) . Also any of those relations could stay empty. It should look like this(for example): Epic contain Feature, Feature contains task and etc. From other hand, BUG does not related to any type and for it the relation filed/link will remain empty. * ***@***.*** maximal number level in hierarchy as maximal number of types * Each type could have few children, but each child may have 1 parent. * Once that structure is defined on organization level, then during their use you need to follow the hierarchy. It means, for example if you create a "feature", then you need to define to which Epic it's related to and etc. For example: If was defined that Story may contain only BUG or TASK, then there are only possible option that visible in interface ***@***.*** * Also it's required to benign able to have a view (or to be able to create a dashboard) which is based on those relations: easily to see the list of Parent Objects and List of their children. With best regards, Maria Katz System Analyst, Engineering Services Haifa, I2M Platform, Philips IT Philips Medical Systems Technologies Israel Advanced Technology Center, Philips Building 34 [Shield_email] From: Riley Broughten ***@***.***> Sent: Tuesday, May 28, 2024 10:01 PM To: community/community ***@***.***> Cc: Katz, Maria ***@***.***>; Mention ***@***.***> Subject: Re: [community/community] Issue Types Private Beta (Discussion #112806) Caution: This e-mail originated from outside of Philips, be careful for phishing. Thank you for your feedback @mariaKatz<https://github.com/mariaKatz>! Could you share some more details on how this would ideally work for your organization and how you'd expect this to work? For example, what is the ideal issue type hierarchy you'd want defined or recommended for your organization? - Reply to this email directly, view it on GitHub<#112806 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BA3HD7IF3OHBX4ENJOKQATDZETH6RAVCNFSM6AAAAABEZSJHECVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TKOBUG4ZDQ>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>

…

________________________________ The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.

[RokeJulianLockhart]

***@***.***

@mariaKatz, the formatting of your response is rather broken. I suggest you visit it via the web GUI rather than e-mail.

[petewalker]

I appreciate this has been asked by many, but is there any timeline for widening this beta out? We would love to test this, particularly in conjunction with Issue Hierarchies whenever they are available.

[rileybroughten]

@petewalker we're expanding this private beta, so please do let me know the name of your organization!

[petewalker]

Thanks @rileybroughten

Could you possibly opt in:

• ltsdigital
• smartstartminds

Thanks!

[rileybroughten]

These have been enabled! Let us know any feedback or questions you have 👍

[petewalker]

@rileybroughten are you also able to add:

https://github.com/exreducation
https://github.com/SalesApe

?

Many thanks! These features are looking great so far 👍

[rileybroughten]

These have been flagged in!

[TylerMatteo]

Hello! It's great to see that this feature is in progress! The Issue for Issue Types on the road appears to show that Issue Types are set at the Organization level. I was wondering if any thought has been given to having them be set at project level? Several teams in my org would love them feature but I could see it be challenging to use if we all have to use the same set of Issue Types. In any case, having this feature at all would be a huge win for us!

[nicksloan]

Not with GitHub, but curious. Do you imagine that an issue of a type associated with one project cannot belong to a different project? Or does it just get treated like an untyped issue?

Could you work around this by prefixing issue types so it is clear what project they belong to?

[rileybroughten]

@TylerMatteo how much would you like to customize the set of issue types available within an organization? Would it be project by project, by groups of repos, etc? Curious how granularly you'd like to define these issue types and any examples you have 😄

[TylerMatteo]

I guess what I was picturing would be project by project, so essentially what is shown in the image above for the Issue types under organization settings, but that page would exist in the setting for a project. Then, ideally, if you wanted to reuse a set of issue types for multiple projects, you could take advantage of Project Templates for that.

My org mostly creates a Project-per-team (as opposed to per....project 😆 ) so it would be helpful to have different types for each. For instance, one team might split work into Bugs and Stories whereas another might just use Tasks, etc.

[jarmak-nv]

+1 to this thought - having per project with the ability to set templates at the org, just like project setups is my ideal. Just like @TylerMatteo says, not all projects need the same info and I really like the flexibility of being able to spin up a short-lived high-focus project (maybe a cross-team effort that's high prio).

I like the flexibility GitHub's issue management offers and doing it at the org level is more restrictive than I think the rest of existing issue management is.

[christinatx]

it would be good for the selection to be editable even when not the author of the issue (ex: programs team needs to make edits)

[rileybroughten]

@christinatx if you have access to edit the issue you should be able to change the issue type once it is added. You can find the option on the sidebar on the right of the issue body under Change issue type

[parkerbxyz]

Feedback: I had a really hard time figuring out how to add or change an issue type because I was looking for it in the same place where you set an issue type upon issue creation. My instinct was to click the Edit button in an issue to bring up the issue type selector.

[rileybroughten]

We're planning to change this placement so it's more prominent and next to where you add and change other metadata, such as assignees or milestones. I'll post an update when this has been done! 👍

[glennsc]

Hey @rileybroughten I see that this change is live! So much easier to find now!

[DHowett]

The new issues experience does not allow you to search for an Author who is not "known" to the repository.

The old experience let you type in an author name and submit it even if the autocomplete did not find it.

The new experience does not let you submit an author name unless it is a member of the repository.

I manage a fairly large repository with a huge number of non-committer issue filers. If I cannot search by their names, I am lost.

[rileybroughten]

Thanks for reporting this! I've filed an issue to look into this 👍

[rileybroughten]

@DHowett we recently pushed a fix for this, let us know if you are still experiencing this!

[phillmv]

1. It's noticeably slower than the previous experience. Unscientifically, I'm getting ~3.5s with the new experience and compared to ~2.5s with the old one. We shouldn't be shipping experiences that are slower.
2. i find that "opened [time ago] by foo" is more readable than "foo opened [time ago]"
3. I find that I would prefer to have the "Filters" dropdown, it makes it more discoverable than autocomplete drop down

i.e.

[peckjon]

When using Issue Templates, is there a way to make the Type immutable (or hidden?) so the Issue submitter cannot alter it?

Also, I think (n=1) that the value for Type is case-sensitive in YAML Templates, which would be worth documenting (and changing to "Bug" in the example above to work with our default types)

[rileybroughten]

There is not currently a way to make the Type immutable or hidden, as it can still be changed in the dropdown during creation and after creation when a template was used.

Using type: 'bug' or type: 'Bug' in a YAML issue template should work with the default issue type of Bug, but let me know if you are seeing something different!

[danemacmillan]

Can you enable this beta for linusshops organization?

[rileybroughten]

Done!

[ashwanthbalakrishnan5]

Hi @rileybroughten ,we would like to give it a try in https://github.com/intergrity-technologies/. Thank you!

[ashwanthbalakrishnan5]

@rileybroughten, can we get access to new issues experience and sub-issues beta too ?

[rileybroughten]

Done!

[DeveloperPaul123]

We would love to give the beta a try and provide feedback for the @xstrahl organization.

[rileybroughten]

This org has been enabled!

[DeveloperPaul123]

Awesome, thank you!

[tal-shani]

Hi @rileybroughten! We at @OneLayerHQ are excited about this feature, especially in conjunction with sub-issues and the new issues experience. Would it be possible for us to participate in the beta and offer our feedback? We'd be thrilled to contribute! 😃

[rileybroughten]

Added!

[dmohns]

Hey @rileybroughten

We would love to participate in beta Issue Tyes, sub-issues and the new issues experience. It looks amazing and I'd very excited being able to do so 😉

Could you add the orgs

• @d-rec
• @EnAccess

to the beta?

[rileybroughten]

You've been added!

[tnordquist-bis]

Hey @rileybroughten,

we are already participating in the beta and are waiting for the GraphQL documentation to assign issue-types to issues.
Is there any progress on that?

[rileybroughten]

We've made additional GraphQL mutations public (behind the feature header) for issue types, see the section Automating issue types for more details! Public documentation is not yet available but let me know if you have questions.

[mpab1410]

If you all are taking certain orgs for the beta, we would love @LoganAluminum to try it out and give feedback (in conjunction with the sub-issues beta as well). We've been evaluating a move away from Azure Boards and would like to see if Github Projects would be a good candidate for us given these two betas.

[rileybroughten]

You've been added!

[RehabAbotalep]

Hi @rileybroughten
When filtering issues by type, it works correctly for all types except "User Story." Attempting to filter by "User Story" results in the following error:

Invalid value for User type

I found that manually adding double quotes around User Story (i.e., "User Story") allows the filter to work as expected. It would be more convenient if this adjustment could be handled automatically, so users don’t need to add the quotes manually.

[rileybroughten]

We have this bug noted and I'll let you know when we have it fixed 👍

[adamtharani]

Hey @rileybroughten

We’d love to partake in testing out the whole new issues experience, types and subtasks. Could you please add @Marketcircle

Thanks

[rileybroughten]

You've been added!

[adamtharani]

Thanks!

[majdfr]

Hi
Same here. We'd really like to be added to the whole new issues experience features (including types, sub issues)
https://github.com/CCFR-SF
thanks

[ChristianFehlinger]

Hi,

I like the issue type; it makes things much easier. I have a question about the built-in workflows in Projects for adding items. I’ve set up several actions to import specific types of issues from different repositories, but I’d also like to import PRs as well.

I assume PRs aren’t imported because of the issue type filter. Is there a way to add logic like '((Issue && (Bug || Story)) || PR) && open', or do I need to create two separate imports—one for issues and another for PRs?

[rileybroughten]

There is not yet a way to specify a filter with that logic. The best way would be to create two separate workflows as you have noted

[mkolar]

Hi @rileybroughten

The work on issues improvements is looking great. We're in the middle of moving all our issue management back to GH projects and would love to join the Beta with @ynput org. The new features seem to fix vast majority of the friction we're seeing at the moment.

[agdebroisemns]

Hi @rileybroughten, can my organization benefit from the Issues Type Private Beta, please?

[rileybroughten]

👋 Issue types are now in public preview 🎉! Moving forward, we will handle all opt-in requests via our waitlist, so make sure to add your orgs there if you haven't already!

As we are moving out of private beta, we will also be closing this discussion in favor of our public preview feedback thread. Please direct all feedback there moving forward.

[EMPACTS]

Hi @rileybroughten

Thank you so much for your dedicated work on Isssue Types Project. As a project manager, I see a huge future of building project management on Github and synchronize our works here.
We have a startup project called @empacts and have already signed up your waitlist. Could you please have a check please? We would love to initialize our project planning with Github Project

Thank you so much!