YouTrack issue states used in .NET tools team and their description



As designed

The behavior described in the issue is intentional. If you find it seriously disruptive or if we’ve misunderstood you, please let us know in the issue’s comments section.


We can’t work on this issue until another one (linked) is resolved.

Can’t Reproduce

We have been unable to reproduce the issue on our side. It could be flaky or fixed already, or we may not have had all the details we needed. If you’re still experiencing the issue and have any further details, please share them.


The issue is the same (or has the same cause) as another one (linked).


If the issue was a bug, it’s been fixed; if it was a missing feature, it’s been implemented.

Fixed In Branch

If the issue was a bug, it’s been fixed; if it was a missing feature, it’s been implemented; the changes are now in a separate branch and haven’t been merged into the default branch yet.

In Progress

We’re currently working on the issue.


Unfortunately we don’t have enough information to proceed. If you’re willing to share any further details about the issue, please do so in the comments.


The part of the product that was causing this issue has been removed or significantly reworked since it was created.


We are currently evaluating demand for the issue and checking whether it requires complicated or risky changes. Please leave a vote or comment if you think it should be prioritized.


We want to implement the fix or feature in the near future. We can’t promise it will appear in the next public release, but it’s on our short list.


We have reviewed the issue and decided that, even though it has merit, we cannot currently include it in our near-term plan.


The team has not yet reviewed the issue.


The issue has been reviewed by the team, but it hasn’t yet been assigned to a specific milestone.

Third Party Problem

The issue is caused by a third party. We've done our best to inform them about it and, if their bug tracker is public, posted a link to the issue.

To be Discussed

We need some time to discuss the issue.

To Reproduce

QA will try to find the steps needed to reproduce the issue on our side.

Under Investigation

We’ve triaged the issue, but now we need to investigate it more thoroughly. This may require processing additional information like logs or dumps.


QA has confirmed that the issue has been fixed.

Verified in Branch

Same as Verified, but hasn’t reached the default branch yet.

Waiting for Info

We’ve requested additional information from the person who created the issue and are waiting for them to get back to us.


We’ve reviewed the suggestion and, while we appreciate its value, we unfortunately do not have the resources to implement it.


The issue was resolved but it has appeared again.


The issue actually turned out to be a question or a misunderstanding, and it has been answered or resolved.

29 out of 43 found this helpful

How long does it typically take to go from untriaged to being in triage ?


We aim to make it no more than a week.


Why do we have so many states? cant we simplify this.


We tried to make the process as transparent as possible, to see both what's going on in the project and what's going on with the specific issue without having to look into comments etc.



If you are going to make it more transparent, this screen should be presented as graph of states, not a table


Please sign in to leave a comment.

Have more questions?

Submit a request