vectorface / fogbugz-global-backlog Goto Github PK

Currently the autocomplete applies the trim before the match along with applying it to all results.

It should apply the 30 character trim only to the sliced results instead of all the objects.

• Allow time changes
• Allow assigned to changes

Would be nice to have this work with web sockets so that someone else can be changing this & see the changes life and or when the cron/worker runs it'd push the changes directly to the user.

As I'm going to be changing the functionality of the autocomplete to accept all tickets no matter the existing state it makes sense to add a status column.

This column will become a little obsolete once I've implemented the sprint backlog

Having used the tool a little bit, it would be simpler to use if items could be re-ordered by dragging and dropping.

A single number on its own in the "Add to backlog" field should be assumed to be a bug number. If a user enters a positive integer in this field, show them the full issue directly underneath as if it was being searched, and allow them to add it to the backlog this way.

bulk reassign
sorting
quick overview of task on hover.

A circle with a line in it is the universal symbol for power on/off. I suggest replacing it with a settings icon (eg: A cog wheel) or similar.

HTML shouldn't be chilling inside of our javascript.

• Add folder in Resources/public for Handlebars
• Create Templates
• Add Handlebars to layout
• Fetch file, parse, compile

This should be decoupled enough to use https://github.com/startuplife/propaganda/issues/3

Eventually I went to end up with something like this with the photo of the assigned person on the left with the color of the milestone behind it kind of like the new gmail app.

Paper Mockup:

Much Inspiration from:

Sprint & product should keep track of the total existing in the current ones.

When adding a new entry it doesn't add 'hours' to column

Forgot to actually finish adding the fogbugz link to the backlog titles

@ihsw mentioned that

phpredis lets you set a custom prefix so that you don't have to set it yourself manually
$redis->setOption(\Redis::OPT_PREFIX, "VectorfaceBacklog:");
(note the colon at the end there)

Currently all the sprint code banks on a single sprint existing.

Needs to be refactored to support sprints

I haven't had much exposure using the jquery sortable & I want this UI to focus around being able to rapidly reorder the lists.

http://jqueryui.com/sortable/

At some point I should look into moving the existing functionality to a team/user level

While I was using the new autocomplete I found it extremely annoying for it to list out the closed tickets when I knew I was looking for a active ticket.

Though I can see the use case to add a closed ticket to a sprint to show progress and therefore I'll just allow the user to toggle between, "Open, Closed, All"

Things need to be cleaned up a bit

• Fogbugz moved out of Command
• Add Twig Extension to allow fogbugz.url_ticket

As the ticket search is moving towards allowing for any state of the ticket to be search it doesn't make sense to automatically tickets from backlog that are closed in fogbugz.

Often people refer to a case with an inaccurate title or only by case #. It would be nice if the search feature could fall back to searching for an exact case #.

Need a product page to list out all the existing tickets in the product backlog

Jon has mentioned he'd like the actual position to go back to fogbugz backlog

Patrick M - "looks good so far, can we put a row number so we can have a count?"

It'd be nice to have a place holder when you click to go to fogbugz for reference sake when you close fogbugz & come back to backlog.

Fogbugz uses Lucene for their searching component and after experimenting I found out that you can't request all tickets using the wild character.

• Plugin system for different
• Authentication
• Reorganizing the list prompts for a save

@ihsw mentioned that

new Response() has a default status code of 200 btw
and since symfony 2.1 there's a JsonResponse() which will encode for you and set the content-type too

Now that I am looking back I think it was a poor choice on my part to use fogbugz naming for reference on things such as instead of calling a ticket id I would put ixBug to match with fogbugz naming convention.

This worked well for coding specifically just for fogbugz but could have been generic without any draw backs...

I made a bad assumption that all ticket titles would be unique and the fact that I store the title as the member in the sorted set means they won't be added.