Messages posted by: jchuet

Christian,

GH does not care about the status nor resolution of the issues.
If you have some issues with some time remaining in it and that are resolved, GH will sum them up also.

GH will not take for granted that a resolved nor issues in certain states have no estimates left.

You need to reset these issues.

Cheers,
JC

Hehe ! awesome Christian.
Thanks for getting back on your thread.

Let us know if you have any other questions.

Cheers,
JC

Yeah we certainly will.
We should be revamping the documentation for GH 4.0

Cheers,
JC

Not yet, but you can add you request in our backlog:
http://jira.atlassian.com/secure/VersionBoard.jspa?selectedProjectId=12200

CHeers,
JC

Hi,

You can enable the listener in your JIRA > Administration > Global Settings > GreenHopper >>> Version Synchronizer.

This will ensure that on every update/create your hierarchies are respected.

It will be the same for the Component Synchronizer.

If you think you have issues that are not respecting the version hierarchies you can simply click on the "Synch" link on top of your column and GH will repair the associations for all defect issues.

Let me know how it goes.

Cheers,
JC

Sure thing!
Glad it worked out.

Cheers,

Yes I would look into the rights (permissions) that your Tomcat user has on the server.
When releasing a version, GH is trying to create a directory to insert your version chart snapshots. If GH fails to create the directory then it will not proceed with the release.

You might want into your logs to confirm that a directory cannot be found.

GH will try to create the directory in the same parent directory as your Indexes. (You can find that path in your JIRA > Admniistration > System > Indexing)

Let me know if this helps.

Cheers,

Hi John,

Yeah this is on the roadmap.
Actually the first one we will attack is the description field.
(Support of wiki markup)

Cheers,
JC

Why dont you attach the files to the issue itself?
Also I think there is a custom field that is a URL that might be used for HTML links.

Cheers,
JC

Wtan, you should upgrade to 3.8
THis issue was fixed.

Cheers,

Yeah of course.
What I would do is create a custom field plugin.
Now if you want this to be included in the GreenHopper stats it must extend the NumberCFType.

Then when getting the value you can see if it is a parent with subs or links in your case. If so return the sum of the subs else return the db value.

If you need more help let me know.

Cheers,
JC

Hi John,

What I meant in that thread is that you can implement your own custom field.
That will imply some code. It is not build in JIRA nor greenHopper.

The implementation is quite straight forward but it does requires coding effort.

Now In GreenHopper 4.0 we have planned to implement what we call a "Theme" It will be a way to associate stories to a theme (like to an Epic in your case). See http://www.greenhopper.com/jira/browse/GHS-706
I think this will answer in a much much better way what you are trying to acheive here.

In other words the Theme will aggregate Points, hours and all stats of all assoicated issues (could be stories with subs, bugs and so on)

Let me know if it does.

Cheers,
JC

So I am a bit confused ...

Did you solve your problem?

If not could you send me a screenshot of:
1) Issue causing the proble in the taskBoard
2) Same Issue standard issue view

Also can you make sure that you are actually capable to transitate the issue via the JIRA standard Issue screen.
If not you might want to log a support ticket to Atlassian

Cheers,
JC

Hi John,

You wont be able to roll up your Story points from your subs.
Also I am not quite sure to understand what you are trying to acheive.
Should'nt you be estimating from up to bottom instead of bottom-up?
In other words estimate your Epics first then your stories that are generated by these epics?

Cheers,
JC

The Attached file should be when Posting a reply not doing a Quick reply no?

Cheers,