[
https://issues.apache.org/jira/browse/BSF-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536724
]
Craig Russell commented on BSF-8:
---------------------------------
I've reset the default assignee for issues. A default assignee is not needed to
get email notifications, which should be sent to the list anyway.
I've added sanka, sanjiva, and nandika to the project. This can be done for
others if you have a jira-administrator on the project.
Is one of the PMC able to take on the JIRA administrator role?
> Set up JIRA for project
> -----------------------
>
> Key: BSF-8
> URL: https://issues.apache.org/jira/browse/BSF-8
> Project: BSF
> Issue Type: Task
> Reporter: Craig Russell
>
> Hi there,
> my name is Rony G. Flatscher, and I am one of the BSF (cf.
> <http://jakarta.apache.org/bsf> committers.
> In the process of migrating from Bugzilla
> (<http://issues.apache.org/bugzilla/buglist.cgi?regetlastlist=1>) to JIRA
> (<http://issues.apache.org/jira/browse/BSF>) we are (short of any knowledge
> and power) lost a little bit and would like to kindly ask for your
> help/assistance with the following problems we have been facing:
> The JIRA project lead is the mailing list address <
> [email protected]>. However, it is unfortunately not possible to use
> this as the default assignee to issues, such that each new entry or change to
> the status of a JIRA issue is automatically mailed to the bsf-dev list, which
> is something very important for us!
> So please, allow for that.
> It is not possible to assing issues to BSF committers, as they do not show up
> on the list of possible assignees, even if they have JIRA accounts already.
> At least the following important users are not showing up:
> Sanka Samaranayake ([EMAIL PROTECTED] or [EMAIL PROTECTED])
> Sanjiva Weerawarana ([EMAIL PROTECTED] or [EMAIL PROTECTED])
> Nandika (probably: [EMAIL PROTECTED], in any case: [EMAIL PROTECTED])
> It has not been possible for us so far to shut down Bugzilla to accept new
> issues and instead forward or tell the user to use JIRA instead!
> Any help *highly* appreciated to resolve these issues!
> Of course, if you have hints/links how we could do that ourselves, we would
> do, but at the moment we are short of any alternatives. (E.g. how can we
> add/remove assignable users for "our" JIRA realm, and the like.)
> Regards,
> ---rony
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
