Messages posted by "jchuet"

OMG! I am still the King!

jchuet — GMT

DING DING DING DING DING !!!! WOAH ! Love it! Cheers, JC :)

OMG! I am still the King!

jchuet — GMT

One to go !

OMG! I am still the King!

jchuet — GMT

OMG !!! I am 3 postss away from 1000!! Sorry dude I need to do it Cheers, JC

OMG! I am still the King!

jchuet — GMT

Haha !!! I am still kicking your butt in the total number of posts in this forum Francois! Start working dude!!! Still have a long way to go ... :twisted: Cheers from Australia, JC

Re:Issue Track/Bug Reporting

jchuet — GMT

Hi Chris, Please send me your email, I will have Nick Muldoon, PM of GreenHopper, to answer you directly on how we manage this in GreenHopper. I have to admit that what we do seems to work pretty smoothly. The dev do not get distracted by the clients issues and we have a pretty good answer/fix rate. My email is jchuet [at] atlassian [dot] com Cheers, JC

Re:name of database element for start date on iteration/release

jchuet — GMT

Sure saach, You can retrieve the XML of the project configuration in the PropertyText table. This one is linked with the PropertyEntry Table. Here is a sample xml you could use: Code:

SELECT *
FROM `propertytext`
WHERE ID = (
SELECT ID
FROM `propertyentry`
WHERE ENTITY_NAME = 'GREENHOPPER'
AND ENTITY_ID = YOUR_PROJECT_ID
AND PROPERTY_KEY = 'CONFIGURATION' )

This will give you the xml. Now the associations are kept in the nodes VERSION_MATCHUP Code:

[entry]
   [string]VERSION_MATCHUP[/string]
   [map]
     [entry]
       [long]11410[/long]  [!-- MASTER VERSION ID --]
       [long]11322[/long]  [!-- CHILD    VERSION ID --]
     [/entry]
     [/map]
[/entry]

I hope this helps. In a very near future this should be kept in a proper dedicated table directly in JIRA since now GreenHopper is fully part of Atlassian. Cheers, JC

Re:Order Hierarchy Report by Greenhopper Ranking

jchuet — GMT

Hi, No the hierarchy plugin is an independent plugin. It is not aware of the GreenHopper ranking field thus cannot sort via this field. In GreenHopper we would like to integrate the hierarchy plugin (or a version of it) more tightly; same look and feel, same interactions, same context (sort, filters, highlights) Cheers, JC

Re:Proper way to release after a sprint?

jchuet — GMT

Can you check if the default context uses a filter? If not I suggest that you enter a support ticket at http://support/atlassian.com Cheers, JC

Re:Proper way to release after a sprint?

jchuet — GMT

Are you applying any filters in your context? The charts will be saved based on your context and preferences.

Re:Create Card Screen

jchuet — GMT

Hi Tenuki, Is your story point field on the JIRA creation screen? GH will try to respect as much as possible the JIRA configuration of your project so if the field is not present in your Issue Type creation screen then it will not appear in the Card creation panel. As for the component selection no this is not supported. The default selection will be based on the planning board right hand side box selection. So if in the Version mode only your FixVersion will be preselected, if in Component mode then the component will be preselected. As for the assignee you might want to take advantage of the automatic assignation of JIRA that is supported by GreenHopper. You can set a leader to your component and then from the project configuration set the default assignee to be the leader o the components. Cheers, JC

Re:Create Card Screen

jchuet — GMT

Hi Tenuki, To add your Story points on your card you will simply need to go in: 1) Tools - Configuration 2) CARD TEMPLATES 3) Add the story point to your "Issue Type" card templates All the fields in your big card template will be injected in your Create Card panel. I am not sure I understand your second question. Would you be able to specify your need with an example? Cheers, JC

Re:Proper way to release after a sprint?

jchuet — GMT

Hi Tenuki, There is actually a build-in feature in GreenHopper that will allow you to release your Sprints. In every fixVersion boxes in the right hand side column of the planning board you will find a release button. (The version needs to be selected) If you click on the button, GH will launch the release mechanism. This one will find all "undone" issues and ask you if you wish to: 1) Ignore the undone issues and release the version 2) Swap all undone issues to another specific fixVersion and release the version ~By undone issues we are talking about issues that did not reach the last column of the TaskBoard.~ Note that using this button will save your current version charts on your server. We call them snapshots. They will all be accessible from the released chart board at anytime. Also if you choose to swap the issues the snapshot will be saved "BEFORE" swapping the issues so you do not loose any data on how the Sprint went. Let me know if this answers your concern. Cheers, JC

Re:How do we configure GH to display 5 char JIRA project keys without truncating down to 2 chars?

jchuet — GMT

Right here: http://jira.atlassian.com/secure/VersionBoard.jspa?start=0&type=VB&selectedProjectId=12200 Cheers, JC

Re:Value Chart?

jchuet — GMT

Hi, Actually the capacity is like a budget. That will set a max by default to your versions. So for instance if you set the max to 15 story points (based on your velocity) the field will turn red in your "iteration" box if you have more then 15 points in your version. It is some sort of notification to let you know that you have committed for more then you can deliver :wink: Cheers, JC

Re:How do we configure GH to display 5 char JIRA project keys without truncating down to 2 chars?

jchuet — GMT

Sorry it is not possible. If you hover the truncated key it will show you the complete key. This was done due to space issues. The numeric part of the key is what should be the most important. You can do your search base on that part. Cheers, JC