[WG: Sakai QA] How to flag JIRA items in indie projects as affecting the release?

[David Horwitz]

Or have a SAK master (Items affecting 2.7 issue) and link the issue ....


D

On 03/29/2010 02:03 AM, Matthew Jones wrote:
> Sounds good, Clone and Move seems like the only way to currently do it. It
> would be nice if you could SubTask->Move but subtasks seem to have to stay
> within the same project space. At least with a Clone it will still retain a
> link on the Jira.
>
> On Sun, Mar 28, 2010 at 7:45 PM, Steve Swinsburg
> <steve.swinsburg at gmail.com>wrote:
>
>   
>> Hi all,
>>
>> I have a query about how to flag an item that is part of an indie project,
>> and has it's own JIRA project, as affecting the main Sakai release? For
>> instance, version 1.2.3 of project A has a bug and no one has fixed it yet.
>> That version is the one that is currently included in, say 2.7.0, so is an
>> issue in the 2.7.0 release. How is this going to get picked up as an issue
>> affecting 2.7.0?
>>
>> I think we'll need to clone the indie issue to a SAK issue, and flag it as
>> affecting a version of Sakai, with a note and a link to the original issue
>> in the other JIRA project.
>>
>> WDYT?
>>
>> cheers,
>> Steve
>> _______________________________________________
>> sakai-qa mailing list
>> sakai-qa at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-qa
>>
>> TO UNSUBSCRIBE: send email to sakai-qa-unsubscribe at collab.sakaiproject.orgwith a subject of "unsubscribe"
>>
>>     
>   
>
>
> _______________________________________________
> sakai-qa mailing list
> sakai-qa at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-qa
>
> TO UNSUBSCRIBE: send email to sakai-qa-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-qa/attachments/20100329/1d714850/attachment.html