Ubuntu-to-RHEL4 Migration Issues#835

Subscribe to Ubuntu-to-RHEL4 Migration Issues 4 post(s), 2 voice(s)

 
Avatar Stephen Murdock 3 post(s) #2225

We recently migrated our Mingle installation from Ubuntu 8 to RHEL4 and imported our main project from an export file. Both platforms use MySQL 5. We noticed immediately that the project displays differently in RHEL4.

One serious issue is that some of the burndown chart lines are flat, where they weren’t before. The data in the story cards for displaying changes in the burndown line are all there, but the chart acts as if they are not.

Another is that all the cards in the preview pages feature links. No links were added previously, and yet all have them now.

Any ideas why the same project should have such drastic differences?

 
Avatar Stephen Murdock 3 post(s) #2235

Same results on Windows Server 2003 (also using the same version of MySQL).

 
Avatar Adam Monago Administrator 254 post(s) #2236

Hi Stephen,

This issue was resolved for you by our support team two weeks ago. My apologies if the solution did not make its way to you or was not clear. I will post it below for the benefit of the other forum users:

The problem did not have to do with their switch from Ubuntu to Red Hat. The problem is caused by a change in the 2.0.1 version of Mingle to which you actually upgraded.

Short Story…. If you make the following changes to your “Burned Down in Sprint” property enumeration values you should be fine:
“Sprint 1” -> ”#108 Sprint 1”
“Sprint 2” -> ”#109 Sprint 2”
“Sprint 3” -> ”#110 Sprint 3”
“Sprint 4” -> ”#185 Sprint 4”
“Sprint 5” -> ”#186 Sprint 5”
“Sprint 6” -> ”#187 Sprint 6”

The “extra links” are a new feature in this version to allow you to click on cards on wiki pages to open the card.

Long Story…. The semantics of card queries have changed in this release:

Before, when you asked for a card in a card query it would return the card name, e.g., “Sprint 1.” The problem with this is that the card name is not unique. E.g., you could have two cards named, “Iteration 1”, one in release 1 and the other in release 2. To guarantee uniqueness we changed card queries to return the card number and name, e.g., ”#108 Sprint 1.” What was happening is that the chart was working with two values, a relationship property value that returned ”#108 Sprint 1” and a text property value that returned “Sprint 1” – the chart was not able to reconcile these values and just kept them at the top of the graph. This is also why their links show as ”#108 Sprint 1” instead of “Sprint 1” on the wiki page now. You can see this most clearly in the x-axis label of their charts between the two versions in the screenshots you submitted to us.

Addendum…. We have just about completed work on adding proper “card” property types. In the next release (2.1) this type of problem should go away, since you will just select an actual card as the property value rather than typing in text.

Thanks,
Adam

 
Avatar Stephen Murdock 3 post(s) #2237

That’s working! Thanks!