You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@bloodhound.apache.org by Apache Bloodhound <bl...@incubator.apache.org> on 2012/11/07 07:34:09 UTC

Re: [Apache Bloodhound] #194: Examine workflow for Bloodhound site

#194: Examine workflow for Bloodhound site
------------------------+--------------------
  Reporter:  gjm        |      Owner:  gjm
      Type:  task       |     Status:  review
  Priority:  major      |  Milestone:
 Component:  siteadmin  |    Version:
Resolution:             |   Keywords:
------------------------+--------------------

Comment (by olemis):

 Recently I noticed some weird transitions while using new workflow .
 Sequence was

  1. #195 put into needsinfo status owner => jdreimann
  2. #195 put into assigned status owner => <empty>
     (even if input box = olemis)
  3. #195 put into assigned status owner => olemis
     (review action not available :'( ... )
  4. #195 put into review status owner => jdreimann

 The issue is somewhere between transitions (2) or (3) . I was hoping to be
 do it like this

  1. #195 put into needsinfo status owner => jdreimann
  2. #195 put into assigned status owner => olemis
  3. #195 put into review status owner => jdreimann

 what d'u think ?

 '''PS:''' the same comment has been posted to bh-dev ML ... I just thought
 this had to be mentioned here instead ... jftr

-- 
Ticket URL: <https://issues.apache.org/bloodhound/ticket/194#comment:17>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker

Re: [Apache Bloodhound] #194: Examine workflow for Bloodhound site

Posted by Olemis Lang <ol...@gmail.com>.
On 11/8/12, Joachim Dreimann <jo...@wandisco.com> wrote:
> On 7 November 2012 06:34, Apache Bloodhound <
> bloodhound-dev@incubator.apache.org> wrote:
>
[...]
>>
>>  Recently I noticed some weird transitions while using new workflow .
>>  Sequence was
>>
>>   1. #195 put into needsinfo status owner => jdreimann
>>   2. #195 put into assigned status owner => <empty>
>>      (even if input box = olemis)
>>   3. #195 put into assigned status owner => olemis
>>      (review action not available :'( ... )
>>   4. #195 put into review status owner => jdreimann
>>
>
> Your suggestion seems reasonable to me, what stops this from working that
> way currently?
>

AFAICS in step (2) username in the input box is ignored and ticket
owner field is set to an empty string once action is applied . Hence
the need for redundant step (3) above .

Besides ... I wonder ... is review action available for ticket owner only ?

-- 
Regards,

Olemis.

Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/

Featured article:

Re: [Apache Bloodhound] #194: Examine workflow for Bloodhound site

Posted by Joachim Dreimann <jo...@wandisco.com>.
Your suggestion seems reasonable to me, what stops this from working that
way currently?

- Joe


On 7 November 2012 06:34, Apache Bloodhound <
bloodhound-dev@incubator.apache.org> wrote:

> #194: Examine workflow for Bloodhound site
> ------------------------+--------------------
>   Reporter:  gjm        |      Owner:  gjm
>       Type:  task       |     Status:  review
>   Priority:  major      |  Milestone:
>  Component:  siteadmin  |    Version:
> Resolution:             |   Keywords:
> ------------------------+--------------------
>
> Comment (by olemis):
>
>  Recently I noticed some weird transitions while using new workflow .
>  Sequence was
>
>   1. #195 put into needsinfo status owner => jdreimann
>   2. #195 put into assigned status owner => <empty>
>      (even if input box = olemis)
>   3. #195 put into assigned status owner => olemis
>      (review action not available :'( ... )
>   4. #195 put into review status owner => jdreimann
>
>  The issue is somewhere between transitions (2) or (3) . I was hoping to be
>  do it like this
>
>   1. #195 put into needsinfo status owner => jdreimann
>   2. #195 put into assigned status owner => olemis
>   3. #195 put into review status owner => jdreimann
>
>  what d'u think ?
>
>  '''PS:''' the same comment has been posted to bh-dev ML ... I just thought
>  this had to be mentioned here instead ... jftr
>
> --
> Ticket URL: <https://issues.apache.org/bloodhound/ticket/194#comment:17>
> Apache Bloodhound <https://issues.apache.org/bloodhound/>
> The Apache Bloodhound (incubating) issue tracker
>



-- 
Joe Dreimann
UX Designer | WANdisco <http://www.wandisco.com/>
*
*
*Transform your software development department. Register for a free SVN
HealthCheck <http://go.wandisco.com/HealthCheck-Sig.html> *