Java code lifetime examples

Daniel Komaz October 8, 2012

Hi,

for our automation-developers I need to ask the following question:

Jira-soap-4.3.2 / SOAP:
Are there any Java source code exmaples showing the life-cycle (create, update, close, ...) of an issue?

Thanks in advance.

2 answers

1 accepted

0 votes
Answer accepted
JohnA
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 8, 2012

Hi Daniel,

I would actually recommend that you the REST API as this is now the preferred platform for Atlassian and the SOAP API will not be bieng developed further, but you can check out the SOAP API documentation here: http://docs.atlassian.com/rpc-jira-plugin/4.4/com/atlassian/jira/rpc/soap/JiraSoapService.html

As stated in our documentation, "Atlassian will continue to support the SOAP API until the REST API provides a replacement for all the existing SOAP functionality." , which means that SOAP will be being deprecated at some point and therefore if possible I would recommend using the REST API instead. You can check out an example of creating an issue with the REST API here: https://developer.atlassian.com/display/JIRADEV/JIRA+REST+API+Example+-+Create+Issue

There are also many other examples of using the APIs on our Developer Site: https://developer.atlassian.com

All the best,
John

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 8, 2012

Um, the question doesn't make a lot of sense.

There is no "life cycle" of an issue in Java. Jira has a workflow engine in it that allows the end user to implement whatever process they need (obviously, there are limitations, gotchas etc). There's a default workflow and an editor in Jira.

There is java code for handling the workflow. But it's totally abstracted from the issues, hence there is no "code for the life-cycle" because the life-cycle is a user defined set of variants.

Could you clarify what you are looking for here? A diagram of the default workflow? Code for pushing things through a workflow via SOAP?

Suggest an answer

Log in or Sign up to answer