+1 for creating a jira component to JSF component mapping.
Don't really care if we use * or sbx or sandbox or just leave them all the same.
The sandbox/tomahawk division is just an indication of
stability/support. I don't see it as an important distinction in the
context of reporting JIRA
On 2/21/06, Sean Schofield [EMAIL PROTECTED] wrote:
I made another improvement to our JIRA setup. I added a Patch
Available state. There is now an operation called Provide Patch
that users can click once they have attached a patch. It will then
place the issue in the Patch Available state.
The sandbox/tomahawk division is just an indication of
stability/support. I don't see it as an important distinction in the
context of reporting JIRA issues.
Exactly.
+1 Sounds ok to me. If not it is hard to find those issues with
patches, and you find the patch when it is not useful anymore because
it was provided some time ago...
Regards,
Bruno
On 2/22/06, Sean Schofield [EMAIL PROTECTED] wrote:
I made another improvement to our JIRA setup. I added a
Hi, I prefer (sandbox) or (sbx), and avoid the *
Bruno
On 2/21/06, Sean Schofield [EMAIL PROTECTED] wrote:
I moved the sandbox stuff but I did not create the components yet.
I'll wait to see what people think about * or (sbx) or whatever.
Also, I deleted the 'other' component so most issues
I have succesfully created a MyFaces Tomahawk project in JIRA. Issues
will have an id of TOMAHAWK-[issue number]. I also renamed the
existing JIRA project to MyFaces Core. The issues for that project
remain MYFACES-[issue number]. I believe we will need infra to
officially group them together
Thanks Sean!
I have moved all of the tomahawk issues (at least the ones marked
tomahawk in the original jira) to the new JIRA project. JIRA is also
smart enough to map the old issue numbers with new issue numbers. So
if you try to navigate to MYFACES-975[1], JIRA knows enough to
redirect
Thanks Sean for the hard work,
+1 from me to put sandox under tomahawk.
Regards,
Bruno
On 2/21/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Thanks Sean!
I have moved all of the tomahawk issues (at least the ones marked
tomahawk in the original jira) to the new JIRA project. JIRA is
may be a silly question,
but how to change / move a bug to a special component
e.g. from other - tree2
Thanks,
Matthias
On 2/21/06, Bruno Aranda [EMAIL PROTECTED] wrote:
Thanks Sean for the hard work,
+1 from me to put sandox under tomahawk.
Regards,
Bruno
On 2/21/06, Matthias
Just click on Edit this issue in the sidebar under Operations and
assign a new component.
Regards,
Arvid
Matthias Wessendorf wrote:
may be a silly question,
but how to change / move a bug to a special component
e.g. from other - tree2
Thanks,
Matthias
On 2/21/06, Bruno Aranda [EMAIL
thanks
On 2/21/06, Arvid Hülsebus [EMAIL PROTECTED] wrote:
Just click on Edit this issue in the sidebar under Operations and
assign a new component.
Regards,
Arvid
Matthias Wessendorf wrote:
may be a silly question,
but how to change / move a bug to a special component
e.g. from
FYI we disabled email notification to the list when you edit an issue
(change the name, description, version or component.) This will cut
down on some our JIRA traffic. Also, no emails to the list when
moving an issue between projects.
The issue reporter, the assignee and watchers will still be
Ah, I see.
Thanks for the informations.
I'll help to *edit* some issues.
So for sandbox, we just create a *component* inside of TOMAHAWK and
*store* all issue under this label, right ?
-Matthias
On 2/21/06, Sean Schofield [EMAIL PROTECTED] wrote:
FYI we disabled email notification to the list
I was thinking of creating one component for each sandbox. So people
who are interested in a particular component can easily see (and maybe
fix) those issues. Perhaps a * character at the end of the component
name to remind us this is sandbox?
Sean
On 2/21/06, Matthias Wessendorf [EMAIL
On 2/21/06, Sean Schofield [EMAIL PROTECTED] wrote:
I was thinking of creating one component for each sandbox. So people
who are interested in a particular component can easily see (and maybe
makes sense
fix) those issues. Perhaps a * character at the end of the component
name to remind us
The only thing I worry about is searching on a * char. Maybe a (sbx)
or something?
On 2/21/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
On 2/21/06, Sean Schofield [EMAIL PROTECTED] wrote:
I was thinking of creating one component for each sandbox. So people
who are interested in a
I moved the sandbox stuff but I did not create the components yet.
I'll wait to see what people think about * or (sbx) or whatever.
Also, I deleted the 'other' component so most issues are now
unassigned to a component. If there is no issue that makes sense to
assign them to they can stay
I made another improvement to our JIRA setup. I added a Patch
Available state. There is now an operation called Provide Patch
that users can click once they have attached a patch. It will then
place the issue in the Patch Available state.
This way we can keep track of issues where patches have
18 matches
Mail list logo
