Embed Notice

@liztai The way Jira is usually used is extremely bad. It’s a specialist tool with (too) many features, a good PM should be able to use a subset of those effectively, but a non-PM worker should preferably be only exposed to an absolute minimum of them by default. Jira doesn’t have any such UI build in though, and most PMs don’t notice how complex it is, so you end up being expected to do PM work in the middle of just trying to do your job – almost anyone would lose focus with so much significant context switching, it’s definitely not just you.

Best solution would be for management to understand how to use Jira, but that’s hard (and Jira doesn’t make it easier). More practical workarounds are to minimize how much you interact with it, just write the absolute minimum in the tickets, set that you are working on them, and don’t touch any of the other features. Management will probably complain that “this ticket is not correctly assigned” or somesuch, but crucially they will now be talking about tickets that are already done. :blobfoxmlem: