Project

Profile

Help

Task #6222

closed

Mark redmine issues as MODIFIED only if a commit is merged into a master branch

Added by ttereshc over 2 years ago. Updated over 1 year ago.

Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

Sometimes when we work on large issues which might last more than one release and it doesn't make sense to merge incomplete pieces into a master branch, development happens in a dedicated branch and PRs related to the feature are merged into it.

Redmine stories/issues become MODIFIED even when commits are merged into other branches than a master one. Also, every time we rebase the branch it adds more revisions to the issue on the redmine side. It shouldn't create the revision until it goes to master branch either. It all makes tracking in redmine more complicated.

With the current merging strategy, every task/story/issue, basically anything, apart from release specific commits, should go into the master branch any way. So the suggestion is to change the state of an issue and create revisions in redmine only when commit is merged into a master branch.

Actions #1

Updated by ttereshc over 2 years ago

Here is an example of the issue with commits which are not currently in the master branch. https://pulp.plan.io/issues/6018

Actions #2

Updated by dkliban@redhat.com over 1 year ago

  • Status changed from NEW to CLOSED - WONTFIX

This is still a problem, but it occurs infrequently.

Also available in: Atom PDF