Hi Dammina,
Firstly I should point out that this project would ultimately be defined
by you and so it is of particular importance that you make this both
challenging enough and realistic enough for you to achieve in the
available time.
You have spotted a very interesting issue that you might want to solve
as part of this project and if I were you I would certainly use this to
strengthen your application. The ability for users to specify details
like ticket type, milestone, components and other fields certainly seems
very desirable to me but there are going to be various solutions to the
problem which will vary in complexity of implementation and actual
usability.
If you come up with some suggestions, we could discuss what the
community would prefer (and there is a good chance that we will make
more suggestions if we can) but remember to continue to balance our
advice with what you think is achievable. You may of course need our
help to understand what may be easy or difficult.
Anyway, it is great to see that you are spotting issues that might be
solved.
Another area you might want to give a little consideration to is whether
there might be anything you could take advantage of from the context
that the list is found in. In case you have not noted, wiki syntax is
available in a number of places including wiki pages, ticket
descriptions and comments.
I hope that answered your question well enough!
Cheers,
Gary
On 04/03/14 12:02, Dammina Sahabandu wrote:
Hi Gary,
Another thing that I wanted to clarify is, by this method we will only be
able to add summaries for the created tickets. May be it will be possible
to fetch the reporter information too. But there are many more important
fields in a ticket that should be filled such as type and priority. So do
we need to address this issue?
Thanks,
Dammina
On Tue, Mar 4, 2014 at 4:03 PM, Gary Martin <[email protected]>wrote:
On 04/03/14 04:32, Dammina Sahabandu wrote:
Hi All,
I'm Dammina Sahabandu, a 3rd year Computer Engineering Undergraduate at
University of Moratuwa, Sri Lanka. Currently I'm doing an internship at
WSO2 inc which is an open source middleware organization. So I do have
experience in several Apache projects (Axis2, Synapse etc.). So as the
first step I did some background research about the Apache Bloodhound
project. And also I did checkout the svn repo and installed
it successfully.
After going through the JIRA list I found several interesting ideas, but
I'm particularly interested in the idea of creating tickets using a
wiki list [1]. So as I understood simply the idea is to provide a button
when there is a list in the wiki(numbered or bullet pointed). And we need
to implement a system to create tickets using the list after the user
clicking on that button. Then we need to update the wiki page(the
relevant
list) replacing the list with the links to the created tickets.
Is that correct? Can you please give me a feedback to clear up the idea.
And it would be really great if you can provide some more details about
the
project.
[1] https://issues.apache.org/jira/browse/COMDEV-110?filter=12326260
Thanks
Dammina
Hi Dammina,
Great to hear from you. For quick reference here, the associated ticket
for bloodhound is https://issues.apache.org/bloodhound/ticket/231
I believe your interpretation of the ticket is reasonable. What has been
stated so far is probably not a full specification for the problem so it
would be worth considering:
* Permissions - who is appropriate for the button to be presented to
and who can use the button?
* Intrusiveness - not all lists will need to be turned into tickets so
could there be means to determine this?
That is a shorter list than I thought I would come out with but feel
free to add to this, Dammina. As this would be your project, it might be
better if you try to answer those questions rather than getting us to
prescribe answers. This may be useful for strengthening your final
project proposal too.
Cheers,
Gary
