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 Josh 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".
• I 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.

On the backend

I also:

• Add new Lindens to PJIRA so they can participate and assign issues to themselves, or be assigned issues by other Lindens.
• Add new release versions when they're released.

Much of the above is manual 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. :)