Page "Proposals/BEP-0011" was changed by dammina Diff URL: <https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0011?action=diff&version=5> Revision 5 Changes: -------8<------8<------8<------8<------8<------8<------8<------8<-------- Index: Proposals/BEP-0011 ========================================================================= --- Proposals/BEP-0011 (version: 4) +++ Proposals/BEP-0011 (version: 5) @@ -18,7 +18,7 @@ == Abstract #abstract -Currently Apache Bloodhound provides a method for creating tickets by filling a form with relevant information. But as it provides the functionality just for add one ticket a time, for a user who requires to create a large number of tickets this could be really tedious process. So the major idea of this project is to implement a functionality which will make it possible for the users to create a batch of tickets at once using a wiki macro. converting !WikiFormatted tables into set of tickets. +Currently Apache Bloodhound provides a method for creating tickets by filling a form with relevant information. But as it provides the functionality just for add one ticket a time, for a user who requires to create a large number of tickets this could be really tedious process. So the major idea of this project is to implement a functionality which will make it possible for the users to create a batch of tickets at once using a wiki macro. ---- == Proposal #proposal @@ -27,12 +27,13 @@ Among other issue tracking systems Apache Bloodhound makes itself uniquely special by providing the best user experience. So though it is important to add new features to Apache Bloodhound we need to be very careful on preserving and improving the usability of the software. The target of the feature I'm proposing to be implemented, will not only add new functionality but also it will boost Apache Bloodhound into a new better user experience level. -Apache Bloodhound already provides a method for the users to track issues by providing functionality of creating tickets. It is a dropdown form which contains the some of the relevant fields to be filled and saved in the backend database. Somehow if the user requires to fill one or more of the other fields that doesn't display in the dropdown he will be redirected into a new page which contains the complete form of relevant fields. If the user just wants add one ticket at a time this method will work fine. But if the user wants to a large number of tickets he has to go over and over again through this process which will be really exhausting experience for the user. As I mentioned earlier one of the major power of Apache Bloodhound is it's great user experience. So it is really necessary to provide a separate method which will make this process easier for the users. +Apache Bloodhound already provides a method for the users to track issues by providing functionality of creating tickets. It is the Quick Create Tickets component which is a dropdown form which contains the some of the relevant fields to be filled and saved in the backend database. Somehow if the user requires to fill one or more of the other fields that doesn't display in the dropdown he will be redirected into a new page which contains the complete form of relevant fields. If the user just wants add one ticket at a time this method will work fine. But if the user wants to create a large number of tickets he has to go over and over again through this process which will be really exhausting experience for the user. As I mentioned earlier one of the major power of Apache Bloodhound is its great user experience. So it is really necessary to provide a separate method which will make this process easier for the users. -So the proposed idea is to provide functionality for the users to batch-create tickets by just converting an existing wiki table into tickets. This engages three major steps. +So the proposed idea is to provide functionality for the users to batch-create tickets by just adding a wiki macro into the existing wiki context. This engages three major steps. -1. User add a ticket table into the wiki. -1. User fills the ticket table. +1. User adds the wiki macro into the wiki text defining the number of tickets that he is planning to create. +1. Wiki macro will then generate an empty table with appropriate ticket fields as columns within the wiki. The table will contain the user defined number of rows. +1. User fills the ticket table with the appropriate ticket data that he wants to create. 1. User clicks on save button to display the created tickets. [[Image(http://i1173.photobucket.com/albums/r600/dammina/Batch-cretetickets.png?t=1395118296)]] @@ -45,7 +46,7 @@ ---- Format of the macro will be: {{{ -[[TicketTable(numberOfTickets)]] +[[BatchCreateTickets(numberOfTickets)]] }}} (Figure 01) ---- -------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 .
