[jbosstools-dev] Change in jira notification

Andersen Max max.andersen at redhat.com
Tue Apr 6 13:33:30 EDT 2010


On Apr 2, 2010, at 05:13, feng.qian wrote:

> Hi Max,
> 
> There is a little case.
> A jira no component, no assignment. Then I set the componet as Web service, but the assignment is not set automatically to the leader.
> This is a issue?

It's just how jira works.

I've added a section in the wiki explaining how to use it:

Rememeber to get automatic assigment for component lead on already assigned issues choose "Automatic" in the Assignment field.

/max

> 
> 
>> Hi,
>> 
>> Based on input from the last two face-to-face meetings I've changed the jira default assignment from being always "Unassigned" to be "Assign to component lead if component has an identified lead".
>> 
>> This means we no longer can use "unassigned" as indicator for if someone got assigned or committed to do the issue but also means you should be getting notifications as soon as an issue gets reported to the components you are leading - thus now more important that ever that you reassign/set-fix-version if issue is not on your plate.
>> 
>> Note, I haven't yet changed the component leads and some still don't have an identified lead so if they are wrong or needs updating then let me know and i'll fix those. Going forward we should get someone identified as lead for every component we have.
>> 
>> I've also updated the "How Developers should use JBoss Tools Jira"-wiki (https://community.jboss.org/wiki/HowDevelopersshoulduseJBossToolsJIRA) to reflect this.
>> 
>> Let's see if this makes us process incoming jira faster :)
>> 
>> /max
>> 
>>   
> 




More information about the jbosstools-dev mailing list