#588: Integrate duplicate relations to ticket workflow
--------------------------+-----------------------
Reporter: astaric | Owner: astaric
Type: enhancement | Status: accepted
Priority: major | Milestone: Release 7
Component: relations | Version:
Resolution: | Keywords:
--------------------------+-----------------------
Comment (by rjollos):
Replying to [comment:5 astaric]:
> If you think that checking the path_info is a better idea than checking
for presence of keys in data dict, commit your change as well.
I don't have a solid argument for making the change at the moment, so I'll
leave it as is. I just mentioned, because checking the `path_info` looks
more familiar to me from all of the plugins I've worked with. One possible
advantage is that you'll send less time in `post_process_request` when
loading the `/newticket` page, but I can't say that is significant.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/588#comment:6>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
