[sldev] Re: Speed of adopting open practices (Re: IJIRA and PJIRA)

[Mike Monkowski]

OK, so you can't make the internal JIRA public and a switch to PJIRA 
seems to be impossible.  You need to figure out a relatively simple 
first step if you want to get more out of open source bug fixing.

How about a version of the SLJiraStats list 
http://www.sljirastats.com/jira_search.php?search=30 for the internal 
JIRA with as much information as can reasonably be made public? 
Obviously there would be no links to the internal JIRA issue details.

Since it's not a direct access to the JIRA, you can filter the 
information as much as you like and display only the columns that you 
feel comfortable displaying, although I would hope that at least Linden 
ID, priority, status, assignee (can be just yes/no if you want), 
created, and updated would be there.

I am also wondering if the internal JIRA has a link to the corresponding 
PJIRA issue that the LL developers can click on.  My guess would be that 
it would be there, but the lack of participation by LL developers on 
PJIRA leads me to suspect that it is not.

Mike


Tofu Linden wrote:
> Mike Monkowski wrote:
>  > You don't have to go full
>> PJIRA all at once.  Read-only IJIRA would be a big step forward, though 
> 
> I totally sympathise - we've been discussing the ramifications of an
> integrated Jira since before the initial open-source release.  There's
> general agreement that an integrated Jira is desirable as a goal, BUT
> for reasons Rob described - and more - this hasn't happened yet and
> won't take the form of automatically throwing our old issues public as a
> rule.
> 
> We use our internal Jira for way, way more than technical bug-tracking,
> plus I'm sure you understand that historical attached data and comments
> written against issues for the context of internal consumption can
> easily contain sensitive information concerning residents (i.e. contact
> information, etc) which was never intended to leave Linden Lab.