You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Animesh Chaturvedi <an...@citrix.com> on 2013/05/03 01:10:56 UTC

[DISCUSS] Jira Component based Filters and Subscription Emails

Folks 

I am working on setting up JIRA filters (named queries)  to show open issues for a given  component.  The idea is whoever is interested in specific CloudStack  components can setup personal email subscription to notify them of potential opportunities to work on. The personal subscription email looks like the following

	From : jira@apache.org
	Subject: [jira] Subscription: XXX where XXX is the Filter Description
	Body: 
 		List of Issues Ids and Summary


Sample Email: 

	From: jira@apache.org
	Subject: [jira] Subscription: CLOUDSTACK-Baremetal-Open-Issues
	Body:

	Issue Subscription
	Filter: CLOUDSTACK-Baremetal-Open-Issues (4 issues)
	Subscriber: animeshc
        
	Key         Summary
	CLOUDSTACK-1619Baremetal - Restore/reset VM fail with java.lang.NullPointerException
            		https://issues.apache.org/jira/browse/CLOUDSTACK-1619
	CLOUDSTACK-1618Baremetal - Stop VM fail
            		https://issues.apache.org/jira/browse/CLOUDSTACK-1618
	CLOUDSTACK-1614Baremetal - Reboot VM fail 
            		https://issues.apache.org/jira/browse/CLOUDSTACK-1614
	CLOUDSTACK-1610Baremetal API addBaremetalPxeKickStartServer fail to prepare PXE server  causing create instance with Kickstart style image to fail
            		https://issues.apache.org/jira/browse/CLOUDSTACK-1610

	You may edit this subscription at: https://issues.apache.org/jira/secure/FilterSubscription!default.jspa?subId=13729&filterId=12323942




To make the subscription easier I can add the subscription link to our component maintainers page. 

The same filters can be used to notify the dev mailing list on a regular basis. There is no direct way to notify the mailing list so I will have to setup a personal subscription for each of these component filters and use mail-client rules to auto-forward the subscription emails to the dev mailing list. 

Do you think this is of value? Please share your thoughts and suggestions.


Thanks
Animesh

Re: [DISCUSS] Jira Component based Filters and Subscription Emails

Posted by David Nalley <da...@gnsa.us>.
On Thu, May 2, 2013 at 7:10 PM, Animesh Chaturvedi
<an...@citrix.com> wrote:
> Folks
>
> I am working on setting up JIRA filters (named queries)  to show open issues for a given  component.  The idea is whoever is interested in specific CloudStack  components can setup personal email subscription to notify them of potential opportunities to work on. The personal subscription email looks like the following
>
>         From : jira@apache.org
>         Subject: [jira] Subscription: XXX where XXX is the Filter Description
>         Body:
>                 List of Issues Ids and Summary
>
>
> Sample Email:
>
>         From: jira@apache.org
>         Subject: [jira] Subscription: CLOUDSTACK-Baremetal-Open-Issues
>         Body:
>
>         Issue Subscription
>         Filter: CLOUDSTACK-Baremetal-Open-Issues (4 issues)
>         Subscriber: animeshc
>
>         Key         Summary
>         CLOUDSTACK-1619Baremetal - Restore/reset VM fail with java.lang.NullPointerException
>                         https://issues.apache.org/jira/browse/CLOUDSTACK-1619
>         CLOUDSTACK-1618Baremetal - Stop VM fail
>                         https://issues.apache.org/jira/browse/CLOUDSTACK-1618
>         CLOUDSTACK-1614Baremetal - Reboot VM fail
>                         https://issues.apache.org/jira/browse/CLOUDSTACK-1614
>         CLOUDSTACK-1610Baremetal API addBaremetalPxeKickStartServer fail to prepare PXE server  causing create instance with Kickstart style image to fail
>                         https://issues.apache.org/jira/browse/CLOUDSTACK-1610
>
>         You may edit this subscription at: https://issues.apache.org/jira/secure/FilterSubscription!default.jspa?subId=13729&filterId=12323942
>
>
>
>
> To make the subscription easier I can add the subscription link to our component maintainers page.
>
> The same filters can be used to notify the dev mailing list on a regular basis. There is no direct way to notify the mailing list so I will have to setup a personal subscription for each of these component filters and use mail-client rules to auto-forward the subscription emails to the dev mailing list.
>
> Do you think this is of value? Please share your thoughts and suggestions.
>

This makes sense to me, we just need to document well how to subscribe.

--David