Page "Proposals/BEP-0011" was changed by dammina Diff URL: <https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0011?action=diff&version=3> Revision 3 Changes: -------8<------8<------8<------8<------8<------8<------8<------8<-------- Index: Proposals/BEP-0011 ========================================================================= --- Proposals/BEP-0011 (version: 2) +++ Proposals/BEP-0011 (version: 3) @@ -79,7 +79,7 @@ ---- ---- -When retrieving the tickets it is required to identify the tickets that have been created. For that the idea is to retrieve based on the creation time. For that it will be require to extend the !TicketQuery macro to handle absolute time stamp values. +When retrieving the tickets it is required to identify the tickets that have been created. For that the idea is to retrieve based on the creation time. For that it will be required to extend the !TicketQuery macro to handle absolute time stamp values. ---- {{{ @@ -97,7 +97,16 @@ == Rationale #rationale -[This section will be completed soon!] +After the user submitting the details the page needs to reload and display a normal ticket query table which contains the details of tickets that have been created. Retrieving the exact tickets that have been created can be solved in different ways, each of them has it's own advantages and disadvantages. Currently I have decided to use a query which will be similar to the following query which retrieves the created tickets on a time based manners. +---- +{{{ +[[Widget(TicketQuery, query="created=2007-01-01 00:00:00..2008-01-01 23:59:59", max=10, title=Batch Created Tickets)]] +}}} +---- +Which requires to get the exact time interval of ticket creation.Otherwise, it will leads to a ticket query table that displays details of the tickets that have been created in a different time which will confuse the user. +Another technique to retrieve these tickets is used the max value in the id column of the database before and after creating tickets. Then write query to display the tickets which has id's between those two values. Currently there is no method to retrieve the max value and there is no method to handle inequalities in a ticket query. So this method will require an extension of the ticket query macro. + +[This section is not completed yet!] {{{#!comment <The rationale fleshes out the specification by describing what motivated the design and why particular design decisions were made. It should describe alternate designs that were considered and related work, e.g. how the feature is supported in other issue trackers or ''Trac'' hacks . The rationale should provide evidence of consensus within the community and discuss important objections or concerns raised during discussion. Take a look at sample rationale below> -------8<------8<------8<------8<------8<------8<------8<------8<--------
-- Page URL: <https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0011> Apache Bloodhound <https://issues.apache.org/bloodhound/> The Apache Bloodhound issue tracker This is an automated message. Someone added your email address to be notified of changes on 'Proposals/BEP-0011' page. If it was not you, please report to .
