[Apache Bloodhound] Proposals/BEP-0011 modified
Page Proposals/BEP-0011 was changed by dammina
Diff URL:
https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0011?action=diffversion=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:
[Apache Bloodhound] Proposals/BEP-0011 modified
Page Proposals/BEP-0011 was changed by dammina Diff URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0011?action=diffversion=6 Revision 6 Changes: ---8--8--8--8--8--8--8--8 Index: Proposals/BEP-0011 = --- Proposals/BEP-0011 (version: 5) +++ Proposals/BEP-0011 (version: 6) @@ -51,18 +51,18 @@ (Figure 01) -[[Image(http://i1173.photobucket.com/albums/r600/dammina/Selection_026.png?t=1395118317)]] +[[Image(http://i1173.photobucket.com/albums/r600/dammina/Selection_002.png)]] 'Figure 01' -As it conveys the macro takes an user argument number of tickets that the user is going to add to the ticket table. Then the macro will be able to render a table with required fields as column headers and numberOfTickets number of empty rows to be filled by users.(Figure 02) +As it conveys the macro takes an user argument number of tickets. That argument defines the number of tickets that the user is planning to batch create. Then the macro will be able to render an empty table with required fields as column headers and numberOfTickets number of empty rows to be filled by users.(Figure 02) Then the user will be required to fill the ticket table with appropriate issue data.(Figure 03) After filling the table the users will be able to click on the save button which will be positioned under the ticket table and batch-create tickets. After that the wiki page will be modified, that is the table will be modified into a normal ticket query table where the ticket id and ticket summary will be links redirecting to appropriate tickets that have been created.(Figure 04) -[[Image(http://i1173.photobucket.com/albums/r600/dammina/Selection_030.png?t=1395118322)]] +[[Image(http://i1173.photobucket.com/albums/r600/dammina/Selection_003.png)]] 'Figure 02' ---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 .
[Apache Bloodhound] Proposals/BEP-0011 modified
Page Proposals/BEP-0011 was changed by dammina Diff URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0011?action=diffversion=7 Revision 7 Changes: ---8--8--8--8--8--8--8--8 Index: Proposals/BEP-0011 = --- Proposals/BEP-0011 (version: 6) +++ Proposals/BEP-0011 (version: 7) @@ -68,7 +68,7 @@ -[[Image(http://i1173.photobucket.com/albums/r600/dammina/Selection_033.png?t=1395118334)]] +[[Image(http://i1173.photobucket.com/albums/r600/dammina/Selection_004.png)]] 'Figure 03' ---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 .
[Apache Bloodhound] Proposals/BEP-0011 modified
Page Proposals/BEP-0011 was changed by dammina Diff URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0011?action=diffversion=8 Revision 8 Changes: ---8--8--8--8--8--8--8--8 Index: Proposals/BEP-0011 = --- Proposals/BEP-0011 (version: 7) +++ Proposals/BEP-0011 (version: 8) @@ -59,8 +59,10 @@ As it conveys the macro takes an user argument number of tickets. That argument defines the number of tickets that the user is planning to batch create. Then the macro will be able to render an empty table with required fields as column headers and numberOfTickets number of empty rows to be filled by users.(Figure 02) Then the user will be required to fill the ticket table with appropriate issue data.(Figure 03) +At this point users will be able to change the number of tickets that is initially planned to create. If the users requires to create some more tickets they can use the `+` button under the empty table, which will append an extra empty row to the empty ticket table. +If the users wants to decrement the batch size they can just mark the appropriate check boxes of the rows that he wants to be removed from the empty table and use the `-` button to remove those rows from the empty table. -After filling the table the users will be able to click on the save button which will be positioned under the ticket table and batch-create tickets. After that the wiki page will be modified, that is the table will be modified into a normal ticket query table where the ticket id and ticket summary will be links redirecting to appropriate tickets that have been created.(Figure 04) +After finalizing the size of the batch and filling the table with ticket data the users will be able to click on the save button which will be positioned under the ticket table and batch-create tickets. After that the wiki page will be modified, that is the table will be modified into a normal ticket query table where the ticket id and ticket summary will be links redirecting to appropriate tickets that have been created.(Figure 04) [[Image(http://i1173.photobucket.com/albums/r600/dammina/Selection_003.png)]] @@ -74,7 +76,7 @@ -[[Image(http://i1173.photobucket.com/albums/r600/dammina/Selection_034.png?t=1395118333)]] +[[Image(http://i1173.photobucket.com/albums/r600/dammina/Selection_005.png)]] 'Figure 04' ---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 .
[Apache Bloodhound] Proposals/BEP-0011 modified
Page Proposals/BEP-0011 was changed by dammina Diff URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0011?action=diffversion=2 Revision 2 Changes: ---8--8--8--8--8--8--8--8 Index: Proposals/BEP-0011 = --- Proposals/BEP-0011 (version: 1) +++ Proposals/BEP-0011 (version: 2) @@ -1,91 +1,156 @@ *Placeholder for Dammina's GSoC proposal* -= BEP 0011 : BEP title #overview += BEP 0011 : Batch create tickets from wiki list #overview [[PageOutline]] -|| '''BEP''' || BEP number || -|| '''Title''' || BEP title || -|| '''Version''' || leave blank || -|| '''Last-Modified''' || leave blank || -|| '''Author''' || Author With Email u...@dom.ain, Author Name Only, or The Bloodhound project (see [wiki:/Proposals#bep-header-preamble BEP preamble explained]) || +|| '''BEP''' || 11 || +|| '''Title''' || Batch create tickets from wiki list || +|| '''Version''' || || +|| '''Last-Modified''' || || +|| '''Author''' || Dammina Sahabandu dmsahaba...@gmail.com || || '''Status''' || Draft || -|| '''Type''' || BEP type (see [wiki:/Proposals#bep-types BEP types explained]) || +|| '''Type''' || Standards Track BEP || || '''Content-Type''' || [wiki:PageTemplates/Proposals text/x-trac-wiki] || -|| '''Created''' || leave blank || -|| '''Post-History''' || leave blank || +|| '''Created''' || || +|| '''Post-History''' || || == Abstract #abstract -Delete text in this section and add a short (~200 word) description of the technical issue being addressed. Take a look at sample abstract below - -This template provides a boilerplate or sample template for creating your -own BEPs. In conjunction with the [wiki:/Proposals general content guidelines] and the [wiki:/Proposals/Formats/WikiFormatting WikiFormatting BEP guidelines] -, this should make it easy for you to conform your own -BEPs to the format outlined below. See [#howto How to Use This Template] for further instructions. - -**Note**: if you are reading this template via the web, you should first try to create a new wiki page by selecting `ProposalsRst` |page template guide|. **DO NOT EDIT THIS WIKI PAGE IN ORDER TO CREATE A NEW BEP! ** - -If you would prefer not to use WikiFormatting markup in your BEP, please see [wiki:/Proposals/Formats/RestructuredText reStructuredText BEP guidelines]. - -== Motivation == - -The motivation is critical for BEPs that want to change the copy of ''Trac'' patched using vendor branch . It should clearly explain why the existing ''Bloodhound'' solution is inadequate to address the problem that the ''BEP'' solves. ''BEP'' submissions without sufficient motivation may be rejected outright. +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 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 batch-create tickets by converting !WikiFormatted tables into set of tickets. + == Proposal #proposal -The technical specification should describe any new features , detail its impact on the components architecture , mention what plugins will be included as a result , whether they are hosted by [http://trac-hacks.org trac-hacks.org] or not , and any other relevant technical subject . The specification should be detailed enough to allow competing, interoperable implementations for any of the current supported database platforms (e.g. ''SQLite'', ''Postgres'', ''MySQL'') and server technologies (e.g. ''Apache HTTPD server'', ''nginx'', ''mod_wsgi'', ''CGI'').. +Built on top of Trac Apache Bloodhound is a software development collaboration tool, including issue tracking, wiki and repository browsing (see:http://bloodhound.apache.org). Bloodhound extends Trac (http://trac.edgewall.org/) with multiple product support, advanced search functionality, ticket relations, a simpler installer and sleeker user interface. Apache Bloodhound recently graduated from the Apache Incubator as a stand-alone Apache project. + +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
