Messages posted by: jchuet

You just need to add your metric as a statistc in GH
To do so you have to click on the "Stats" link on top of your column in the planning board and add your "Story points"
This will add you story point in your version boxes and add the set of charts in the ChartBoard.

Cheers,
JC

Hi,

If you log work during a non working day (i.e weekends or a manually added day) the time will be credited to the last working day.
So in other words all logs made on saturday or sunday will be drecited to the friday.

So to answer your second question if the firday is part of your first version then the logs will be credited to that version if of course the issues belong to that version.

If they belong to the version starting on the monday then the Original time of the chart will be reajusted.

Hope this helps.

Cheers,
JC

Sure you will find all documentation of GH here:
http://confluence.atlassian.com/display/GH/Home

Also we have just released the GreenHopper 101 here:
http://confluence.atlassian.com/display/GH/GreenHopper+101

Cheers,
JC

HI Arne,

Glad it helped.

Cheers,
JC

HI Arne,

TODO ==> All issues corresponing to the first column mapping
IN PROGRESS ==> All issues corrsponding to the second column up to the second last column mapping
DONE ==> All issues corresponding to the last column mapping

Hope this helps

CHeers,
JC

Hi Boris,

No worries.

As for now we only support the Number field and not the drop down.
But like I said in my previous answer, we do have a request to support it.
It will certainly meet your need.

Yeah the ranking field is actually what you will use to prioritize your issues.
Quite handy

In a very near near release we will focus on a "wizzard" to help with all this boring and not so easy configurations/settings. You are learning the hard way but that will make you a better JIRA user

Cheers,
JC

Hi Boris,

To add story points in your GreenHopper projects you need to:
1) Add a Custom field of type Number (with Number Searcher) and associate it to the projects and issue types that will use it via the JIRA > Administration > Custom Field
2) Add the field to your issue card templates via the Agile > Tools - Configuration > CARD TEMPLATES
3) Add the field as a statistics via the "Stats" link on top of your planning board column

1) and 2) will provide the field to your selected issue type (like Story)
3) Will add the stats in your version boxes and add a set of charts accessible via the ChartBoard (like burndown, burnup, velocity charts)

The number field in the cards is a free text so the only constraint is for the entry to be a number. There is no restriction on the number itself.
We do have a request to support dropdowns as for points. This one will allow to restrict the value of the feild to a set of values.

I hope this helps.
You can always visit our doc here: http://confluence.atlassian.com/display/GH/GreenHopper+Quick+Start+Guide
Early next week we will be publishing GreenHopper 101 with some best practices and "how to" step by step configurations.

Cheers,
JC

God you are fast ievers ...

This is actually the first time I see this issue raised.
Did you guys performed any backup restore before shuting down JIRA?

The backups should not be needed.
Anyhow your JIRA should be backing up automatically if you do not have an automatic backup of your database in place so GH is being backuped.

Now the only other reason I see is the shutdown itself.
Something might have happend. A concurent update of the database while JIRA was shuting down.

Cheers,
JC

Hi ievers,

I think your problems comes from your TaskBoard mapping.
Simply go into your project > GreenHopper > configuration > TASKBOARD MAPPING and verify that you columns are properly mapped.

If not simply correct the mapping.

GreenHopper should now react better in the PlanningBoard and TaskBoard.

No worries on the data side, GH does not alterate any data.
It is just displaying whatever you have in JIRA. Here it seems that GH for some reasons (might be a problem in the sutdown) lost track of the mapping thus the computation of the progress bar is wrong.

Let me know if this solves your issue.

Cheers,
JC

Hi Benoit,

You will need to create some context that are sorted by the ranking field in your PLanning board.
These ones will be reusable in the popup.

Cheers,
JC

What we do is create a dummy fix version called "Obsolete" that acts as a trash can but that we do not purge for historical and traceability reasons.
Then we do a bulk edit via the Issue navigator and move these issues in that version (that is released). It will clean up your backog (unscheduled).

We normally do this before our backlog maintenance.

Cheers,
JC

This is how I do it for the ranking field:

Code:

 
     <customfield-searcher key="exactnumber" name="Number Searcher" i18n-name-key="admin.customfield.searcher.exactnumber.name" class="com.atlassian.jira.issue.customfields.searchers.ExactNumberSearcher">
         <description key="admin.customfield.searcher.exactnumber.desc">Allow searching for a number which exactly matches.</description>
         <resource type="velocity" name="view" location="templates/plugins/fields/view-searcher/view-searcher-basictext.vm"/>
         <valid-customfield-type package="com.pyxis.greenhopper.jira" key="greenhopper-ranking"/>
     </customfield-searcher>

Hope this helps

Cheers,

YAY !

Cheers,
JC

Hi,

1) Look if your ranking field is associated with all issue types.
If not you must do it else you will fall on something similar
2) Look in your card template if there is a field that you have deleted via JIRA. Based on the id of the field that was the first field you have created in JIRA. Could it have been deleted? if so you will need to withdraw it from the template manually. THis will better handled in GH4.0

Cheers,

What does your data export says?

Humm you are on 3.5.
I think you will have a more accurate chart in the latest version of GH.
GH was not handling time estimate resets very well in the earlier versions.

Would you be able to upgrade and see if it changes?

Cheers,