Project

General

Profile

Forums » Problems or support »

Scrum Usage Issue---Important FOR fixing(Thanks Much)

Added by an li over 9 years ago

1.Scrum Board-Draging issues to let the state change has bugs---not cosistent with the issue workflow defined

1)In Redmine workflow setting, we have configured the issue workflow, e.g. tracker: task, there are only 3 states, new->in the progress->done, and fix done cannot be reverted to in the progress and new state.
But I tested in scrum board, if I drag a closed task to "in the progress" panel, there is no block message to block this operation, the state can be changed freely.

2)Another bug is if we define different flow with different states for different tracker, e.g. tracker: bug has 4 states, new->in the progress->resolved->done, for a task, it can not select "resolved" state,
in scrum board, if I drag a task to the state "resolved",it should be blocked, but now, it can change any state freely in the scrum board.

I think these 2 are very important issues to be fixed, for it will leads wrong operations and make the definded workflow valid.

2.When creating a subtask using scrum board, the default "spint" field is filled in with the relevant user story sprint filed, it is very nice. But if I create or update an issue with task tracker or other trackers which the scrum plug-in settings choosen, form the Issue page,not from the scrum page, I think "Sprint" filed shall be left blank, for maybe not for agile usage. If it is auto filled, developers may forget to delete it. Only Spring field be auto filled in the scrum page.

It is reported in the last post.But I detailed described again, if in the scrum page, it is OK, but if create a new issue or updating a new issue in the "issue" page, I think "Sprint" filed needs not be auto filled.


Replies (5)

RE: Scrum Usage Issue---Important FOR fixing(Thanks Much) - Added by an li over 9 years ago

And aonther 2 Questions

1.Only 1 backlog is permitted to create now, that is Product Backlog, right?

2.I found pending effort can be filled easily through a box in the task card, but also I double click the task card, can edit with another redmine default effort, it will be displayed on the left side of the task card, too, why not using redmine default effort field, why adding pending effort field, what are the difference?

RE: Scrum Usage Issue---Important FOR fixing(Thanks Much) - Added by an li over 9 years ago

By the way,I really appericate your work, I compared with other agile plug-ins, it is really the best I try, hope to get reply and improvement good news:)

RE: Scrum Usage Issue---Important FOR fixing(Thanks Much) - Added by an li over 9 years ago

I found pending effort can be filled easily through a box in the task card, but also I double click the task card, can edit with another redmine default effort, it will be displayed on the left side of the task card, too, why not using redmine default effort field, why adding pending effort field, what are the difference?
--------------spent time can be edit when double clicking the task card, pending effort VS Spent Time, what are the differences, for burndown chart, which will be used?

an li escribió:

And aonther 2 Questions

1.Only 1 backlog is permitted to create now, that is Product Backlog, right?

2.I found pending effort can be filled easily through a box in the task card, but also I double click the task card, can edit with another redmine default effort, it will be displayed on the left side of the task card, too, why not using redmine default effort field, why adding pending effort field, what are the difference?

RE: Scrum Usage Issue---Important FOR fixing(Thanks Much) - Added by Emilio González Montaña over 9 years ago

Fixed on version #172, ready to be downloaded on Files section.

RE: Scrum Usage Issue---Important FOR fixing(Thanks Much) - Added by an li over 9 years ago

Hi, I posted issues I tested in scrum 8.0 version, for these issues, I cannot test if now issue drag&move can be limited by default redmine workflow.

Emilio González Montaña escribió:

Fixed on version #172, ready to be downloaded on Files section.

    (1-5/5)