GSoC 2014/bug-set-creator: Difference between revisions

Line 77:
'''POSSIBLE NEXT ITERATION:''' This interface is likely going to be accessed/modified by a number of people at once. I've currently addressed this issue by having a per-bug save button. What do you think about modifying the page to allow real-time collaboration, ala MoPad or Google Docs, et al.? No clicking "Save" or page refreshes required.
 
=== Shauna'sUser Feedback ===
 
=== Shauna ===
 
I want to be able to add bugs from projects OpenHatch doesn't track. For instance, WelcomeBot's issues are not tracked. This could be in the form of freehand entry bugs.
Line 108 ⟶ 110:
* '''e:''' We will store annotated bugs in their own table, and use a many-to-many relationship between lists and bugs. That way, if bug A is in lists 1, 2, and 3, editing bug A on the list 1 screen will make changes for lists 2 and 3 as well.
 
 
=== Catherine's Feedback ===
 
It would be nice to have a bookmarklet-type button I could install in my web browser that would add the URL I'm currently on to my bug list. Then I could browse for bugs in the original project's bug tracker and add them very easily to my target list. I think bookmarklets are very easy to write, provided that you have an API (preferably a RESTful API). Many applications (like Django) have plugins to make exposing a RESTful API really easy.
* '''e:''' This is a really neat idea that could be a cool add-on for a later project iteration.
 
 
=== Jessica's Feedback ===
 
If the application is importing bug information directly from the trackers, it will need to be updated frequently.
Anonymous user