I'd like to configure a Context via the GreenHopper API. When I say Context, I mean the thing named Context in the user interface that has a Name, a Sort By Field and order, a Filter and Criteria, and a Highlight Filter and Criteria. It's unclear to me what that object is named in the API and how to modify it. I see BoardContext, Contexts, and Context. How do I set the current Context – in the UI sense – and how do I change its fields via the API?

Hi
Could you please provide me with a code for how to get a value of the version's "start date".
Or please explain how can I do this.
Thanks

Hi Kenneth,

Are you using the LinkProvider to add an action to the list in the drop down?

Thanks,
Nick

Updating Atlassian Status to reflect availability of GreenHopper LinkProvider Plugin documentation, which can be used in GreenHopper 5.2.

Hi there (again )

When pressing the Cog button on an issue (on fx the planning board) i get a drop down list of possible operation/actions. Is it possible to add issue specific operations to this list?

Kind regards
Kenneth

I have actually succeed in placing a web-item in the operation-operation section on the issue screen. I will present a page where i can choose a master version and an optional subversion (using the greenhoppers hierarchy). The moves seems to work flawlessly.

No unfortunately we will not provide any API or doco before Oct. 2010 as stated in the "Atlassian Status" above.

For your operation, seems quite complex to implement via a simple Issue operation since you will need to select the destination version. You wont be able to achieve this proactively via the drag and drop of GH. The only solution I see is via the "Epic" screen. Jump to the Issue Navigator then bulk edit the issues to move them into another version. But then again there are no way to enforce that the destination version is a "Master"

I will think it a bit more though.

Cheers,
JC

The goal is the following: I need to make a "move to version" issue operation, that moves an Epic and all related user stories + subtasks (we have a epic-label on user stories to add another "level" of issues) to another version. And such i would like the operation to be able to only be able to choose "master" versions to move to.

I looks like that i am able to do this with your help in above comment. I will try Thanks alot for the quick reply.

Btw. Do you have any documentation regarding the GreenHopper 5.0 API for developers? I am having trouble finding it

Hi Kenneth,

What would be your goal for the move to version?
You know you can build a simple JIRA listener and catch this event.

For the hierarchy you can access it via the BoardContext.
Here is an example:

BoardContext ctx = new DefaultBoardContext(yourProject, theUser);
VersionAssociations associations = ctx.getVersionAssociations();
LinkedList<Long> hierarchy = associations.getHierarchyOf(myVersionId);

Where hierarchy would be populated with all the version ids in the hierarchy ended by myVersion.
[my version id, direct parent of my version id, direct parent of the parent of my version id, ....]

The API of GH should be accessible to the other plugins so you should not have any problems creating your BoardContext.

Cheers,
JC

Hi there.

I am developing jira plugins for my company, and we need to be able to access GreenHoppers functionality/model. Fx we would love to be able to access its "move issue to version" functionality and also it hierarchy of versions. Fx getting master version etc.

Is it possible with the newest GH and Jira 4.1? If not, any workaround?

Kind regards
Kenneth Houmark