Project

General

Profile

bug #19

Under certain conditions, recurrence don't keep assigned person

Added by lupa18 2 months ago. Updated about 2 months ago.

Status:
closed
Priority:
urgent
Assignee:
Target version:
Redmine version:
4.0.x

Description

When it re created, the assigned person get unassigned

Selección_948.png (80.3 KB) Selección_948.png lupa18, 2019-08-19 19:42
Selección_954.png (49.3 KB) Selección_954.png lupa18, 2019-08-21 15:06
13
14

Token votes

History

#1 Updated by cryptogopher 2 months ago

  • Status changed from new to in progress

Thank you for reporting!

Please provide following:
  • plugin version
  • plugin configuration settings
  • recurrence settings
  • number of first recurrence (relative to the issue that has recurrence configured), where assignment failed

#2 Updated by lupa18 about 2 months ago

14

cryptogopher wrote:

Thank you for reporting!

Please provide following:
  • plugin version

1.3

  • plugin configuration settings

SET AUTHOR: author of previous
KEEP ASIGNEE: unchecked
ADD JOURNAL: unchecked

  • recurrence settings

"Copy issue every 1 week, based on due date of last recurrence. "

  • number of first recurrence (relative to the issue that has recurrence configured), where assignment failed

Not sure, maybe first or second.

Now I have new problem. Several issues are created when It must be only one:

All was created yesterday at the same time :-/

#3 Updated by cryptogopher about 2 months ago

  • Target version set to 1.3
  • Redmine version changed from 3.4.x to 4.0.x

#4 Updated by cryptogopher about 2 months ago

  • Status changed from in progress to feedback

lupa18 wrote:

  • plugin configuration settings

SET AUTHOR: author of previous
KEEP ASIGNEE: unchecked
ADD JOURNAL: unchecked

If you leave "Keep assignee from previous recurrence" option unchecked, plugin does not copy assignee from previous recurrence. In such case assignment proceeds according to your Redmine configuration for new issues. I don't see anything wrong here.

If you disagree: please describe what behavior do you expect. Also give us the assignments for all of the created recurrences, including the base issue. You don't need to provide real names, just nicknames.

Now I have new problem. Several issues are created when It must be only one:

All was created yesterday at the same time :-/

Please report new problems in separate issues to avoid confusion. Once you open new issue please provide following:
  • description of recurrence scheme,
  • start and due dates of issue where you configure recurrence scheme,
  • start and due dates of issues created by plugin.

#5 Updated by lupa18 about 2 months ago

cryptogopher wrote:

lupa18 wrote:

If you leave "Keep assignee from previous recurrence" option unchecked, plugin does not copy assignee from previous recurrence. In such case assignment proceeds according to your Redmine configuration for new issues. I don't see anything wrong here.

If you disagree: please describe what behavior do you expect. Also give us the assignments for all of the created recurrences, including the base issue. You don't need to provide real names, just nicknames.

Ok, I misunderstood, because the text: "if unchecked, default assignment rules will apply" and I had interpreted other thing.

You can close.

I will monitor the other error and if persist I will open new issue.

#6 Updated by cryptogopher about 2 months ago

  • Status changed from feedback to resolved

lupa18 wrote:

Ok, I misunderstood, because the text: "if unchecked, default assignment rules will apply" and I had interpreted other thing.

I added small clarification to option description in 684b5f54

Closing issue.

#7 Updated by cryptogopher about 2 months ago

  • Status changed from resolved to closed

Also available in: Atom PDF