@antoviaque How would we measure time on a ticket that includes both upstream and non-upstream work?
For example, if we’re working on a frontend plugin and create frontend slots for it, the work will likely be in the following categories:
- Changes to the MFE to support plugins (CC work)
- The actual frontend plugin (non-CC work)
- Cherry-picks to our custom branches (non-CC work)
- Deployment config and deployment of client code (non-CC work)
Do we need to track all this separately? The time spend in these categories can vary widely from ticket-to-ticket.