Feedback for new issue viewer in projects

[azenMatt]

Select Topic Area

Show & Tell

Feature Area

Issues

Body

We just released (or are in the progress of releasing if you are still seeing the old one) a new issue viewer for when you open an issue inside of a project.

This issue viewer now includes:

• Timeline events
• The project picker (so you can edit projects in addition to the current project)
• Faster performance

Most importantly this is a first step to having a single implementation of the issues page we can use across GitHub. In the future this page will be coming to the repository so we would love your early feedback!

What are your thoughts on this new issue viewer? Is anything missing vs the old one? What could be better? What do you like?

We will continue to release updates as we work on parity against the main repository issue page (eg transfer an issue) on a regular cadence.

The below is an example from our public roadmap of how the new issue view looks:

Guidelines

• I have read the above statement and can confirm my post is relevant to the GitHub feature areas Issues and/or Projects.

[daveyholler]

I'd like to see links be clickable in the project details section of the sidebar:

[azenMatt]

Good spot - we will get that updated

[Darlfas1]

Thanks so much for the hard and good works. I can't wait to see us done and dusted in readiness for Mainnet.

[janakerman-form3]

Previously when I used to copy + paste the title of an issue I was viewing, I'd get a nicely formatted link along the lines of My Issue Title#0000. This made it really easy for me to paste the issue title with a link. That no longer seems to work in the newer view. Thanks.

[joerj123]

It all just feels so sluggish. Adding labels or tickets to task lists takes forever. Please make it faster!

[azenMatt]

Hi @joerj123 - we just pushed an update to improve the performance for adding labels and milestones. Does this feel better to you now?

[bprice6]

Updates still lag for me >5 seconds to the point where it makes me wonder if I added or not.

[miyataka]

I want the behavior of editing an issue to be the same as the behavior of editing an issue from a project.
Specifically, I want tab input in the text area when tab is pressed. Now the latter moves focus away from the textarea.

Thanks.

[azenMatt]

👀 this is how issues have always worked. If you are in a comment-box, tab will take you outside the comment box.

Or am I miss-understanding the component you are referring to here?

[miyataka]

@azenMatt
Thank you for your reply!!!
Something like this.

• Screen.Recording.2023-08-24.at.2.43.43.mov
• Screen.Recording.2023-08-24.at.2.45.37.mov

[zaguiini]

I do not always want to open the issue as a modal. Previously, the issue title had a link. Now, only its number has it. It was easier before, and I can't see a good reason not to bring this wider clickable area back.

[Alfagun74]

also related: https://github.com/orgs/community/discussions/62400#discussioncomment-8238950

[juanmaguitar]

Hi @azenMatt!
We're using a project to link issues and PR's from different repos and organizations with custom fields. We seem to have lost the capacity to access these custom fields for the issues that belong to external repos.

[juanmaguitar]

Warning
TL;DR - It seems there's been a change in GitHub projects that doesn't allow to have issues in a project where the issue belongs to a different organization or already belongs to another project

To provide more context, I will explain this issue with a few screenshots:

As a team, we have our own project to organize our work. This project belongs to the organization "Automattic". In our custom project we add issues from different repos and some of them belong to different organizations (like "WordPress")

In the following snapshot, you can see an issue (from WordPress / developer-blog-content) added to our project dashboard (at Automattic / Projects / Bifrost Sprints).

In the snapshot, it can be seen how this issue belonging to another org/repo contains the value sprint:"🅱️ Sprint Q3-4" as one of the custom fields we defined exclusively for our project.

If we click on the issue we get the following card of the issue that doesn't contain either our project or any of the custom fields we defined for that issue for our project. If we try to change the project, our Bifrost Sprints) doesn't appear in the list of available projects for this issue.

In summary, we cannot access, view or edit, the custom fields we defined for our project in issues from other orgs/repos which was something we could do last week, and it was one of the main reasons we chose GitHub projects to organize our work (as we deal with issues from different repos)

[japf]

👋 @juanmaguitar thanks for the report, we're currently taking a look 👀

[japf]

@juanmaguitar our team just shipped a change to address this feedback. To be more specific: when you view an issue in orgA from a project that is owned by orgB we'll now always render all projects from orgA and projects from orgB. If you view the issue directly, we'll only render project from orgA.

Please let me know if that is fixing your scenario 🤞🤞🤞

[juanmaguitar]

Hi @japf,
Yes, the issue is solved now 👍
Thanks a lot for the fix!

[Darlfas1]

That was a great report. Thanks so much.

[Imran92]

When creating an issue, if I try to add a label, I can select a label from the dropdown but the selected label doesn't appear under Labels in the Modal

[japf]

👋 Hey from the Issues team, I'm not able to repro this scenario. Could you share the steps you're following? You mention "when creating an issue" but it looks like your screenshot is about editing an issue?

[kraftbj]

Thanks for adding clickable links in the sidebar for custom fields... but, for the life of me, I couldn't find a target to click on to edit it. We imported everything from Asana and removing some old Asana links. I ended up inspecting the DOM, deleting the link, and expanding the 's height in order to trigger the button for editing.

[azenMatt]

Thanks - yes this isn't working as well as we want it to and has also caused some accessibility concerns. We are going to need to revert it but will find a better implementation

[mctaylorpants]

I just noticed a small UI issue which I think might be a regression, since I believe this was working the other day:

When editing the "description" field of an issue in the issue viewer, the textarea is missing the handle on the bottom-right that allows you to expand the textarea. Here's what it looks like in the issue viewer:

... and here's what it looks like in the normal full-screen page:

Super minor thing and probably browser-specific, but it does seem like it might be cut off on the issue viewer.

[japf]

👋 Thanks for reaching out, yes this is a regression that happened yesterday. We're about to deploy a fix 🤞

[japf]

Resizing the comment box is back 🎉

[jasell]

The new layout requires way too much scrolling!

• In the new layout the key information of the issue is to far down.
  I want to see the Assignee, Project section in the top.
  Either below the title or after the fist post.

• To improve layout you can reduce fontsize for the issue title as well
  Currently the title consumes 2 to 5 rows in large font, which is a big part of the screen

[Antzed]

+1, the key information needs to be on the top

[wafer-bw]

+1, things are too bloated. Elements need to be more compact.

[vforvova]

Previously select lists for custom project fields had gray text with descriptions to the side (after the actual item name), and now they are missing. Would be nice to have them back - they help quite a bit.

[japf]

👋 Thanks for the feedback. We just shipped a change to add those descriptions 🚀

[SydAirey]

Why did you guys take away the copy link button?! Please put it back!

[francescolaffi]

Was going to ask the same, glad it's just moved 👍 not sure if the icon is self-explanatory for everyone though

[mishmanners]

Oh neato. I'll be using that.

[jayalberts]

Had mild panic attack thinking copy button was gone 😅

[treeder]

I had the same panic attack until I found that copy button. 😆

[EdwardSalkeld]

Same. I use this a lot. Totally missed that.

[bobcats]

One of the reasons I loved having "open in a new tab" easily available was because it's only possible to quickly create "sub-issues" from a checklist on an issue on the full issue show page. If we could bring that experience to the issue panel in a project, that would be sweet!

[japf]

👋 Thanks for sharing this feedback, we're aware and we just started working on that. I don't have a timeline to share yet but we agree this is an important feature we need to have in the new issue viewer 🚀

[mishmanners]

This looks really cool! Can't wait to try it out.

[Flucadetena]

Hi something that has been very tedious for our team since the beginning is that the project does not appear on their "Your projects" section. Even if they are a member of the project.

We tried moving the project to an organization but all the issues and assignments to the members would be lost. So for now their are stuck having to enter my page and searching for the project.

It would be nice if the projects you are a part of just appear on "Your projects" section, even if you are not the owner.

[azenMatt]

Does the global projects page accessible via the left hand nav menu help here?

IMO this is a bit of a confusing navigation pattern, but in general all the links via the left menu are global and the right menu are personal.

[Flucadetena]

Ohhh! Great thanks! That is very confusing indeed. Hope they change it.

[Flucadetena]

It would be very nice to have the ability to link tasks with each other in the roadmap view. Making them dependent of each other. So if one is moved / delayed, the rest of the task move forward that same amount.

It would make roadmap updates sooo much easier.

Thanks for the great work, our team is loving the tool.

[kazwata]

Tasklist block removal dialogue is too wide...

[japf]

👋 Thanks @kazwata for the feedback. We're exploring a newer iteration of tasklist blocks right now so I don't think we'll revisit this in the short term. Please continue to share feedback though, it's super useful to us on the Issues team 🙇

[SydAirey]

Not sure if this was mentioned already because there is a lot of feedback here but I notice that my custom sprint field dates do not match with what pre-populates from the quick view. I have attached a few examples to show below:

The first screen shot are the custom dates I chose in the workspace settings but when I am in the quick view adding issues to the project and their sprints, it shows the pre-populated sprint fields. see below:

Its only a day off and not a huge deal because once I go into the issue itself, it reflects the custom date ranges but just wanted to make sure you guys knew about it.

[japf]

👋 @SydAirey that's a good catch, I just created an issue internally for us to take a look.

[macMikey]

am i dumb? did i forget how to CRUD labels?
i'm editing via the card view. i click on the gear to edit labels and...i see labels that i can assign to the card, but i don't see how to CRUD labels. i thought that was where we went to do that? if it isn't, what is the gear for?
i thought clicking on the label "labels" was for assigning labels, and the gear was for CRUD.
i found the label mods in repo issues, but it would be much nicer if we could modify labels in the project, again.

[SydAirey]

You have to open it in a new tab to see the edit labels button

[snatvb]

On real project not enough templates for tasks and duplicates - would be great to have it

[markcarroll]

Looking great. Still not able to enter emoji such as 🐛 etc into the title bar with autocomplete replacing with the 🐛 character, etc. We still have to open up the full page to do that.

[japf]

Thanks for the feedback @markcarroll, I just created an issue for us internally.

[jay-babu]

Previously, creating a branch and then creating a pull request for the branch would update the issue to link the pull request instead of the branch itself. this no longer works correctly. i have to manually link the pull request

[azenMatt]

Thanks for sharing - we will get this fixed

[human-bee]

When. I convert a ticket in Projects to an issue, I'm no longer allowed to assign the ticket to anyone.

[ken-tan3]

Do not embed a feature "press enter once&save the content" because people who need to convert local lang from alphabet cannot type in correct. It occurred in the title in split board with alpha version.

[loraxster]

Something broke recently. When I create a new item, then click on it, edit, save changes - then try to Convert to issue - this pop-up appears and won't go away. Pop-up should not be appearing (I saved my edited changes).
With the pop-up showing, now I need to go ahead and select the repository. then click the X on the pop-up to make it go away.

[alexz707]

Is there a way to see the history (like in a normal issue) for fields which are only present in the project view?
E.g. we have a prio field which is only in the project view and not on the issue itself.
At first the ticket does not have a prio when it was created. If someone now adds the prio "high" I do not see when & who changed this field.

[trusktr]

I don't see a way to add an issue link (f.e. so that one issue is blocked by another issue). I see the ability to link pull requests, which is similar. This would link issues to make issues dependent on other issues.

For now, I state this in the issue description.

[akleinvm]

Can we make the audit trail collapsible? It can be distracting—especially when there’s no other information on the issue.