Issue Types Private Beta #112806
Replies: 51 comments 88 replies
-
this looks awesome! Is it possible to enroll to private beta for this? |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
This looks great! Would love to participate in the beta. |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
Can I be added to the Private beta please? I can test with a few orgs. |
Beta Was this translation helpful? Give feedback.
-
Hi, |
Beta Was this translation helpful? Give feedback.
-
Hello, |
Beta Was this translation helpful? Give feedback.
-
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.
|
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
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! |
Beta Was this translation helpful? Give feedback.
-
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) |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
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) |
Beta Was this translation helpful? Give feedback.
-
@rileybroughten Would you mind adding https://github.com/ReserveSense to the private beta as well please? |
Beta Was this translation helpful? Give feedback.
-
Hi @rileybroughten could you please add the https://github.com/Cellenza-RD org to the private beta? Thank you! |
Beta Was this translation helpful? Give feedback.
-
Hi @rileybroughten we would absolutely love to give this a try! Looks to be a game changer :D. Could you add https://github.com/ScriptionAI to the private beta please? |
Beta Was this translation helpful? Give feedback.
-
Hi @rileybroughten would love to try out this issue-types feature and provide feedback! Here is our org: https://github.com/Iconem/ Thanks! |
Beta Was this translation helpful? Give feedback.
-
@rileybroughten, this looks great, we would like to give it a try in @fortran-lang. Thank you! |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
The @caddyserver organization would like to try the new issues! |
Beta Was this translation helpful? Give feedback.
-
Hey Riley can our org be added so we can try out these features https://github.com/planning-devsecops-fdc |
Beta Was this translation helpful? Give feedback.
-
Hi @rileybroughten would love to try out this issue-types feature and provide feedback! Here is our org: https://github.com/forus-coop/ Thanks! |
Beta Was this translation helpful? Give feedback.
-
Hi @rileybroughten. I desperately need this to finally migrate everyone away from Jira. If you are still accepting applicants, can you please add @sellsmart-com-au and @PatonaIM and @teamified2. 🙏 |
Beta Was this translation helpful? Give feedback.
-
I'd love a way to convert labels to issue types (similar to "convert to discussion"). Because in bigger projects it is a time consuming process. |
Beta Was this translation helpful? Give feedback.
-
I would like to have custom fields per issue type. For example:
|
Beta Was this translation helpful? Give feedback.
-
Also, Is it possible to disable changing issue type by users? Because in labels if there was an issue template, users couldn't modify any of them. Now they can create issue from bug template, but change type to feature. |
Beta Was this translation helpful? Give feedback.
-
@rileybroughten issue types supported in gh cli? and if not then any ETA for that feature? |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
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.
Improvements to Issues
You’ll see an enhanced experience when creating, viewing, and managing your issues on GitHub.
From the repository, we’ve updated the filtering experience to give you autocomplete suggestions so you know how you can build your searches and what qualifiers are supported.
As you create your issues, there is an improved flow when filling out your issue, as well as being able to select
Create more
to quickly create issues back to back.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
anduntyped
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, delete, and enable/disable them for repositories, as well as 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
.Query IssueType
Returns fields for issue type i.e. private, enabled etc.
Query Issue.IssueType
Returns issue type based on issue ID
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.
Query issueTypes using global search filter API
Org wide searches for issue type.
Coming soon
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.
Beta Was this translation helpful? Give feedback.
All reactions