Please read before using JIRA

[Jeremy Thomerson <je...@wickettraining.com>]

If you use our JIRA for tickets, please note the following couple of
reminders:

   - Do not clone an issue that was closed as "wont't fix", etc.  Just
   reopen and comment if you have a new use case that should be submitted.
    This way we keep all history together in the same issue.
   - Do NOT set the "fix version".  The developers will set that when they
   actually fix it.  If you set it, it may not show up on our radar, or may not
   get into the changelog.  You SHOULD set the "affects version", but NOT the
   "fix version".

-- 
Jeremy Thomerson
http://www.wickettraining.com

Re: Please read before using JIRA

[Martin Grigorov <mc...@e-card.bg>]

Hi Jeremy,

On Tue, 2010-06-01 at 13:19 -0500, Jeremy Thomerson wrote:
> If you use our JIRA for tickets, please note the following couple of
> reminders:
> 
>    - Do not clone an issue that was closed as "wont't fix", etc.  Just
>    reopen and comment if you have a new use case that should be submitted.
>     This way we keep all history together in the same issue.
I just want to note that a Jira user cannot re-open a ticket which is
not created by him/her. Only the reporter or a developer can do that.
Commenting on a closed ticket is not good option because it is easily
lost in the traffic. You and we know that devs cannot answer immediately
on every comment in Jira and later devs do not re-read the comments in
closed tickets ... 
>    - Do NOT set the "fix version".  The developers will set that when they
>    actually fix it.  If you set it, it may not show up on our radar, or may not
>    get into the changelog.  You SHOULD set the "affects version", but NOT the
>    "fix version".
>