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 <de...@bloodhound.apache.org> on 2014/01/15 17:20:43 UTC
[Apache Bloodhound] #742: Duplicate relation can't be set on action
other than "fixed"
#742: Duplicate relation can't be set on action other than "fixed"
-----------------------+-----------------------
Reporter: rjollos | Owner: rjollos
Type: defect | Status: new
Priority: major | Milestone: Release 8
Component: relations | Version:
Keywords: |
-----------------------+-----------------------
Duplicate relations doesn't support a non-default workflows which may
define an action other than //resolve// with the `set_resolution`
operation. This was reported on the
[http://markmail.org/message/nnywu6ybkcd6ugsk mailing list].
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/742>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #742: Duplicate relation can't be set on
action other than "fixed"
Posted by Apache Bloodhound <de...@bloodhound.apache.org>.
#742: Duplicate relation can't be set on action other than "fixed"
------------------------+-----------------------
Reporter: rjollos | Owner: rjollos
Type: defect | Status: accepted
Priority: major | Milestone: Release 8
Component: relations | Version:
Resolution: | Keywords:
------------------------+-----------------------
Changes (by rjollos):
* status: new => accepted
Comment:
On the server-side, [attachment:742.patch] is needed. On the client side,
the duplicate id input is appended to `action_resolve_resolve_resolution`,
and we need to make that more flexible so that is gets appended to any
action that defines a //resolve resolution//. As part of #710 I've been
doing some refactoring of this !JavaScript code, so I'll finish up that
work before returning to finish this ticket.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/742#comment:1>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #742: Duplicate relation can't be set on
action other than "fixed"
Posted by Apache Bloodhound <de...@bloodhound.apache.org>.
#742: Duplicate relation can't be set on action other than "fixed"
------------------------+-----------------------
Reporter: rjollos | Owner: rjollos
Type: defect | Status: closed
Priority: major | Milestone: Release 8
Component: relations | Version:
Resolution: fixed | Keywords:
------------------------+-----------------------
Changes (by rjollos):
* status: accepted => closed
* resolution: => fixed
Comment:
(In [1560598])
0.8dev: //resolve as duplicate// now works correctly for any action with
the `set_resolution` operation. Refs #742.
Previously, the //Duplicate ID// input would not be displayed for any
action other than //resolve//. Also the `duplicate` attribute would only
be bound in `ITicketManipulator` when the action was named `resolve`.
Now a //Duplicate ID// input will be attached to the workflow action and
the `duplicate` attribute will be bound by `ITicketManipulator` for any
action with the `set_resolution` operation. This has been tested and
functions property when there are multiple actions that specify the
`set_resolution` operation.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/742#comment:2>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #742: Duplicate relation can't be set on
action other than "fixed"
Posted by Apache Bloodhound <de...@bloodhound.apache.org>.
#742: Duplicate relation can't be set on action other than "fixed"
------------------------+-----------------------
Reporter: rjollos | Owner: rjollos
Type: defect | Status: closed
Priority: major | Milestone: Release 8
Component: relations | Version:
Resolution: fixed | Keywords:
------------------------+-----------------------
Comment (by rjollos):
(In [1560613])
0.8dev: Fixed error in unit test revealed by [1560601]. Refs #742.
The parent ticket should not have status //closed// since the //resolve//
action is being invoked on it. This error was revealed after [1560601]
since we are now looking up operations for the action, which depends on
ticket status. With the default workflow, //leave// and //del_resolution//
will be the only operations for a closed ticket.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/742#comment:3>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker