Hi Taher
Response inline
Thanks
Sharan
On 2016-09-06 12:37 (+0200), Taher Alkhateeb
wrote:
> Hi Sharan, Everyone,
>
> Great work on the JIRA ->
> https://cwiki.apache.org/confluence/display/OFBIZ/Guidelines+for+Using+Jira
>
> I like the fact that you denote all
Hi Michael
Responses inline.
On 2016-09-06 12:55 (+0200), Michael Brohl wrote:
> +1 on the Wiki page effort, it's great!
>
> Not sure about the issue importance: for me, this is more an indicator
> of how much this issue affects the project instead of a priority to
Please forget about my statement about priority, it IS Priority what we
are talking about...
Sorry for the confusion,
Michael
Am 06.09.16 um 12:55 schrieb Michael Brohl:
+1 on the Wiki page effort, it's great!
Not sure about the issue importance: for me, this is more an indicator
of how
+1 on the Wiki page effort, it's great!
Not sure about the issue importance: for me, this is more an indicator
of how much this issue affects the project instead of a priority to deal
with it. I would leave it as that and maybe introduce a new field for
priority (if we do not already have
Hi Sharan, Everyone,
Great work on the JIRA ->
https://cwiki.apache.org/confluence/display/OFBIZ/Guidelines+for+Using+Jira
I like the fact that you denote all issues for trunk as being either minor
or trivial. This does not mean they are not important or do not contain a
lot of hard work.
Hi Sharan,
I saw you created
https://cwiki.apache.org/confluence/display/OFBIZ/Guidelines+for+Using+Jira
In this thread I suggested
We could start by extracting this section
I think one thing we should consider before all the rest is Jiras issues with patches. Those are more valuable than others and patches have a
disconcerting tendency to become stale, we should avoid that.
I have a rule for that (I did not invent it, thanks Internet): the 10 min rule. If I
Hi Taher
+1
You have raised some good actionable points here. I think you are right that
the Jira guidelines need be completely separated out into something that is
clear and can be used as an easy reference.
I will create a wiki page to start pulling the information together.
Thanks
Sharan
Le 03/09/2016 à 07:56, Taher Alkhateeb a écrit :
- Add a wiki page (if one does not exist) documenting:
- Guidelines for writing JIRA mentioning clarity, provision of solution.
- A clear definition of priorities (blocker, critical, major, minor,
trivial) with some examples.
We could start
+1, jira cleanup is an important step that should be taken care as soon as
we can.
Kind Regards
Ashish Vijaywargiya
HotWax Systems - est. 1997
On Sat, Sep 3, 2016 at 11:26 AM, Taher Alkhateeb wrote:
> Hi Everyone,
>
> As of this writing, we have 3 blocker, 6
Hi Taher,
I fully agree with your analysis of the overall state of our Jira issues!
Except the first two statements but simply because I haven't had a
deeper look in the mentioned issues yet.
I'd like to help with the guidelines if we decide to have them.
Regards,
Michael Brohl
ecomify
Hi Everyone,
As of this writing, we have 3 blocker, 6 critical 733 major, 521 minor and
50 trivial open JIRAs and I note:
- I think none of the blocker and critical JIRAs belong in that category.
- It is also unrealistic to have 733 major issues. it is like saying we
have that many serious
12 matches
Mail list logo