HOWTO work on related tickets

[blaisep]

### Multi-ticket relationships

As a contributor I want to work on distinct features/unit of work toward the same goal so I can track the activities independantly and still conserve a relationship to the larger goal

Background: The new tutorials SHALL include a automated script to run the commands described in the instructions. So a reader can manually follow the steps to learn to use a feature AND a CI can run tests to validate the code examples.

Current Scenario: Both meejah and blaisep create trac issues for the automation. Meejah's ticket is for a spefific tutorial and blaise's ticket is for the general category of tutorial automation. In principle, the general ticket should describe:

• common goals of tutorial automation scripts
• discovering new automation scripts
• instructions for integrating scripts into CI

Blaisep created [Automate the NEW tutorial commands](​https://tahoe-lafs.org/trac/tahoe-lafs/ticket/4113) which is related to a similar ticket created by meejah.

• how can I find a related ticket ?
• how should I described the relationship between the two?
  • Parent/child?
  • Sibling?
  • shared dependency?
  • Unit of work vs Unit of functionality (in a CRUD feature the units of work may be different)
• when I find that ticket, how can I link the tickets together?

Challenges:

• Searching for meejah's ticket:
  • the owner filter returns too many results
  • which keyword to use?
  • Adding a *optional filter* to the query called Milestone AND selecting "User Documentation" from the pop up

## Questions raised about Trac vs Gitea/Forgejo?

• How tickets/issues are related to each other?
  • Parent/child:
    • Trac: not supported
    • Gitea/Forgejo?: not supported
  • Comment refering to another ticket/issue
    • Trac: no reference
    • Gitea/Forgejo?:

### Observations

In practice there is not much process in the current trac tickets. We don't risk breaking very much if we just migrate the existing components, milestones, keywords etc.