User:Torley Linden/PJIRA

This page details what I do on PJIRA, aka Public JIRA, aka the Issue Tracker. It's a lot of meta-stuff involving increasing education of how to use it, housekeeping and maintenance, and tying up lots of loose ends.

On the Resident-facing side

I:

• Resolve fixed issues with their correct statuses — "Fixed Internally" if not yet in a public release, or "Fixed" if it is available to the public. Specifically, after Joshua Linden or someone else makes a release post to the Official Linden Blog, I parse the release notes for PJIRA issues, open them up, and resolve them accordingly.
• Link related issues together so they can be easier found.
• Resolve duplicate issues and link those, too, so Residents can find the open issue we're focusing on.
• Sync external issues with internal ones, meaning: if an Issue Tracker report very closely or exactly matches an issue in our internal systems (aka LLJIRA), I make sure that they're linked to each other — see the "Linden Lab Issue ID field".
• Retitle issue summaries as appropriate, e.g., if the original isn't clear enough, too long when it could be simplified, or missing an important piece of info.
• Add new release versions when they're released so they can be selected as "Affect/s Version".

On the Linden-facing side

I also:

• Add new Lindens to PJIRA so they can participate and assign issues to themselves, or be assigned issues by other Lindens.
• Forward relevant issues to the right Lindens so they can action them further (e.g., a sculptie issue goes to Periapse and Qarl Linden, or a First Look: Voice issue goes to our Voice Team). Wish there was an easier way on an issue's own page to email it to someone.
• Connect issues internally and encourage Lindens to look on PJIRA for newest Resident comments.
• Import issues both during formal bug triages and my own scouting for further investigation. Bugs with useful info such as a solid reproduction are far more likely to be imported, simply due to how actionable they are.

That covers most of it, but there's always more work to be done.

Much of the above is manual, hence why I'm involved, but it's better than not communicating at all — I hope for a future when we have a single, unified issue tracker, but that time is realistically far away, so until then, I'm continuing onwards and upwards, as they say. :)