Problem: can't send people a direct link to a problem

Sometimes I want to share a problem with someone, but I can't do this because problems do not have direct links.

Problem: can't take action in relation to problems

I changed the structure of the events to put opcodes in tags instead of in content, so now nothing works.

Problem: problem tracker event IDs are not very useful to humans

when viewed in regular clients, problem tracker events publish an event ID in the content. This is kind of helpful but not really

solution: use the title of the problem in content instead of publishing the event ID

Problem: can't re-open a closed problem

Problem: many unrelated comments are displayed on problems

There are a lot of unrelated comments displayed when opening a problem.

This is due to the tag structure.

Solution: parse the tags somehow to find comments that should be displayed and reject the ones that should not

Problem: can't see how long a problem has been claimed for

People sometimes claim problems and disappear, leaving it in a locked state.

Maintainers can free these problems, but they shouldn't do this unless the time the problem has been locked for exceeds 432 blocks.

Solution:

Display how many blocks a problem has been claimed for

Problem: rocket indicator on problems reverts back to nostrocket when it shouldn't

At the top-right of a problem there is an indicator showing which rocket currently owns the problem.

This works for the root problem associated with each rocket, but sub-problems display "nostrocket" even when they are nested under a problem that is owned by a different rocket.

Problem: can't view problems by context

I want to be able to view problems based on what context they are applicable to.

For example, I want to see which problems are related to the Engine repository, but not spaceman. If I could tag problems with the relevant repository and filter by this, that would be great.

Some other things I might want to filter by are langauge, difficulty level, etc.

Solution:

Implement a state machine that administers tags.

Tags should have types, e.g. `language`, `repository`, `difficulty`.

Problem: when viewing a single problem, its context in the tree is not clear

When you view a single problem, there's no indication of where it is in the tree and how it relates to other problems.

Solution:

Add parent problems in a similar way to how closed problems are currently displayed in the tree (title only, small size).

Also display children the same way.

Problem: can't change the Rocket taged on a problem once set

Sometimes problems need to move between different Rockets. For example, I just logged a problem about the Flame Bucket Rocket being unable to recieve payments, but this is a problem that should be fixed by Nostrocket even though it is nested under Flame Bucket.

This is currently not possible.

Solution: patch the Problem state machine event handler to allow this.

Problem: can't link existing problems to each other

A "child" problem is a dependency of a parent problem. This is an explicit and direct relationship. A parent cannot be closed unless all children are closed.

But sometimes you go to log a problem, and find out that someone else has already logged it under a different parent. In this situation, the child problem is a dependency of both parents.

To avoid needing to log the same problem multiple times, we should be able to simply link any problem as a dependency of any other problem.

Caveat: need to prevent circular dependencies.

Problem: have to abandon problem in order to create sub-problems

When I claim a problem to work on it, I often find that the problem is not scoped narrowly enough and I want to add sub-problems.

Solution: allow the creation of sub-problems if you are the person who has currently claimed the problem to work on it.

When the sub-problem is created, the Engine should automatically remove the claim on the parent problem.

The main issue for me here is that all the problems are semi-expanded on first view. This means lots of scrolling. Plus like many users I'm accustomed to a list of issues that I can click into to comment, reference, etc.

Problem: Comments on problems don't show attribution

I commented on "Problem: the Nostrocket problem tracker is clunky and annoying to use" and while I can see my comment, nobody else knows it was authored by me. At least I'm not seeing the attribution from Spaceman. This means bad behavior may persist longer than it would if attribution were clear. It also makes it hard to carry on a conversation using the usual @user convention that people are used to.

Problem: Comments on problems don't show attribution

I commented on "Problem: the Nostrocket problem tracker is clunky and annoying to use" and while I can see my comment, nobody else knows it was authored by me. At least I'm not seeing the attribution from Spaceman. This means bad behavior may persist longer than it would if attribution were clear. It also makes it hard to carry on a conversation using the usual @user convention that people are used to.

Problem: Comments are in newest-first order

Comments are currently in newest-first order, which may be good if you're familiar with the situation and want to just see what's new. I believe most viewers will be seeing for the first time and attempting to read the history in chronological order.

#### Solution: A PR is forthcoming to make the order chronological.

I got this running which was very simple, so that's awesome. Also created a sub-problem about comment ordering and a PR to solve it. I have another quick change of the color for comments from this dark-greenish to a little lighter blue and I wonder if I should just PR it or create a sub-problem for that. I guess it'd be good to discuss more problems before implementing solutions but I'm trying to understand how formal the process should be as of yet.

Problem: When there are many comments, the problem view opens with the view at the bottom

When clicking "read more..." on an individual problem with many comments, the view opens scrolled-down. This assumes the user is mainly interested in the comments, however it seems best to open at the top so the problem description can be read first. Same behavior seen in Chrome and Firefox.

#### Solution: Start with the view at the top of the page.