Redmine

Szymon Nowak wrote:

Is there any magic in this functionality? I'm using redmine (~10 people team) and for some of us association between commit and issue via (keywords refs, fixes, close etc) works fine, but some of us can't see Associated table in Issue's details.

Can you check if this might be related to missing permissions (:view_changesets)?

Are there any conditions when association is created? Mayby issue has to be in state "In Progres" before commit or something like that [...]

Not that I'm aware of.

Unfortunately it's not related to permissions.

This error really can't be produced deterministically. Somethimes i see revision on Associated revision's list and somethimes not. I don't know how it works. Once i made those steps:

1. Created Issue
2. Changed status to "In Progress"
3. Commit changes with message

Something changed. 
closes #<id>

Next time I've made identical steps and i can't see association.

• Root
  • Sub1
  • Sub2

And repository is linked only to project "Root", Sub1 and Sub2 don't have configured repositories. In fact it's shared repository for all subprojects in Root

Is there any way to remove all associations from issues and force Redmine to scan repository and re-create all associations? Because it looks like it's not dynamic.

Right now i've tried to add this same repository to subProject, but it causes double count spent time tags
Every commit was counted twice and issues have double Associations (one from repository from Root project, and one from Local prject's repo).

I've not tried to remove repository from Root project and add it to each subproject only. It's not what i want even if it could work. I'd like to add repository only to Root (because each subproject has this same repository) and map commits to all issues in project and all subprojects.

It looks like that Redmine lost some associations, but i really don't know why.

Any idea? I think projects hierarchy cause this issue, but i don't know exactly how to fix it.