Redmine

Cool ！

Once you are used to the GUI then it creates a Wow factor!

Nice!

Note that the plugin should be renamed to: redmine_backlogs after the git clone action.

I get an error creating the charts with rake redmine:backlogs_plugin:generate_chart_data:

rake aborted!
SQLite3::SQLException: near "from": syntax error: SELECT * FROM "backlog_chart_data"     WHERE (backlog_id=1 AND extract(year from created_at)=2009 AND extract(month from created_at)=9 AND extract(day from created_at)=3)  LIMIT 1

I had only one issue and one sub task, any idea what is wrong?

Hi Hans,

Sorry about that. I had to remove a PostgreSQL-specific condition to fix the problem. Please pull from the master branch where the fix is.

Regards,

Mark

That error is solved indeed, now I regret to say I get another one when generating the charts:

rake aborted!
SQLite3::SQLException: no such column: true: SELECT sum("items".points) AS sum_points FROM "items"  LEFT OUTER JOIN "issues" ON "issues".id = "items".issue_id  LEFT OUTER JOIN "issue_statuses" ON "issue_statuses".id = "issues".status_id WHERE (parent_id=0 AND backlog_id=1 AND issue_statuses.is_closed=true)

I'm a little too fond of PostgreSQL, it seems. ;-) Fix has been applied to both master and 0.0.1

The demo looks great. Good idea providing one for people to play with. Three suggestions from the short time I used it:

1. I work across a lot of projects at once, so it would be useful to have a cross project backlog (hence my Stuff To Do and Kanban plugins).
2. The green color in a bit intense with a lot of items.
3. The drag and drop isn't really explained. On my plugins I changed the mouse cursor to the move icon when hovering over something that is draggable. It's a simple CSS rule:

li.issue, li.project { cursor: move; }

As a fellow Agile plugin developer, I'm interested to see where you take this. I think it might be useful for everyone who's developing Scrum / XP / Agile / Your methodology here plugins to share some notes and maybe see if the effort can be shared.

Eric Davis

Thanks Eric. I'll take your suggestions into consideration.

I originally planned on creating a global view of a user's tickets across projects but decided I'll just work on making Backlogs compatible with your Stuff To Do or Kanban plugin. Something to look forward to in the future. :-)

The immediate need is to make this easier to use during the daily stand up activity.

Hi,

The Github link at the top post is broken as I've deleted the 0.0.1 branch and converted it to a tag.

v.0.0.1: http://github.com/relaxdiego/backlogs/tree/v0.0.1

master: http://github.com/relaxdiego/backlogs/tree/master

Sorry for any inconvenience. Still learning the ropes with git. :-)

Mark

Mark M wrote:

I originally planned on creating a global view of a user's tickets across projects but decided I'll just work on making Backlogs compatible with your Stuff To Do or Kanban plugin. Something to look forward to in the future. :-)

Works for me. I'm thinking Kanban would be the better of the two. I learned from my mistakes in Stuff To Do and used that knowledge with Kanban. There's still the issue of exposing cross-project data that needs to be solved but I'm hoping the upcoming Groups feature of Redmine will make that easier.

Sorry for any inconvenience. Still learning the ropes with git. :-)

Let me know if you need a hand, I'm not a Git pro (yet) but I'm using it for everything these days.

Eric Davis

I've found a little bug in the GUI: when there's raw HTML inside a

 block of an issue description, the HTML (including JavaScript) gets rendered.

That's how my post should've looked like..

Alexander Pánek wrote:

I've found a little bug in the GUI: when there's raw HTML inside a pre-block of an issue description, the HTML (including JavaScript) gets rendered.

Anyways, thanks for this great plugin!

Alex

Hi Alex,

That's expected. The description allows textile markup only and a limited number of html tags for security reasons. same as how redmine treats descriptions and notes. :-)

http://www.redmine.org/help/wiki_syntax.html

Regards,

Mark

Hey Mark,

of course, one of those html tags being "<pre>", where you should be able to put html/js code in whatever form and be sure that it’s not being executed/rendered. In my case, there’s a simple view snippet of a script tag for some Google Maps inclusion, yielding an alert box. This shouldn’t happen.

Regards, Alex

Hi Alex,

Ah. Sorry about that. Will check later. :-)

Regards,

Mark

Alexander Pánek wrote:

Hey Mark,

of course, one of those html tags being "<pre>", where you should be able to put html/js code in whatever form and be sure that it’s not being executed/rendered. In my case, there’s a simple view snippet of a script tag for some Google Maps inclusion, yielding an alert box. This shouldn’t happen.

Regards, Alex

Fix applied to master

Mark M wrote:

Alexander Pánek wrote:

Hey Mark,

of course, one of those html tags being "<pre>", where you should be able to put html/js code in whatever form and be sure that it’s not being executed/rendered. In my case, there’s a simple view snippet of a script tag for some Google Maps inclusion, yielding an alert box. This shouldn’t happen.

Regards, Alex

Fix applied to master

Awesome, that was fast - thanks! :)

There is a naming clash with another plugin (ticket grouping) which uses also a field called parent_id in the issues table.
Your plugin is using the same field (parent_id) but then in the items table.

So I you use unique naming in your code w.r.t. this field then it should solve my issue using both together.
(correct me if i am wrong)

We already consider this using the sprint planning when a more stable/mature version is available!

Hi Hans,

It should work alright. I specifically avoided modifying any of the Redmine core tables so that the plugin won't end up clashing with another. Since the parent_id you refer to is in the issues table, it should be fine.

However, test it thoroughly anyway just to be sure (I don't have time to test it myself). And if you do, kindly share your findings for the benefit of everyone else. :-)

Hi Mark,

Thanks for the prompt response. There is a name clash indeed, when calling the redmine_backlogs plugin it gives the following error:

ActiveRecord::StatementInvalid (SQLite3::SQLException: ambiguous column name: parent_id: SELECT "items"."id" AS t0_r0, "items"."issue_id" AS t0_r1, <snip>    WHERE (issues.project_id=5 and parent_id=0)

I think the last bit of code should be :

WHERE (issues.project_id=5 and items.parent_id=0)

Work around: when I remove the issue.parent_id column manually then the backlogs plugin works.

Hi Hans,

Try the parent-id branch I just pushed to github:

http://github.com/relaxdiego/backlogs/commits/parent-id

The URL should be http://github.com/relaxdiego/backlogs/tree/parent-id

in the Issue on my Redmine i have three required custom field

- I tried to create a new item
- On the $REDMINE_CORE/vendor/plugins/redmine_backlogs/app/models/item.rb in line 85 (method save changed to save! for processing error on save)

def self.create_issue(params, project)
...
    issue.save!
    issue.reload
    issue
end

i have the exception on validation because the required field did not filled

Hi Alexey,

Thanks for the feedback. The current version doesn't support required custom fields yet (We don't use that internally). I'd be happy to accept patches though. :-)

Hi Mark,

I think you missed a line in app/models/item.rb" line 95:

  def self.find_by_project(project)
    find(:all, :include => :issue, :conditions => "issues.project_id=#{project.id} and items.parent_id=0", :order => "position ASC")
  end

Now it works