Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Mylyn/JIRA Connector"

m
 
(27 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
[[Category:Mylar]]  
+
[[Category:Mylyn]]  
  
−
== 2006-10-13 Planning Session ==
+
Atlassian has ended support for the Atlassian JIRA connector See [https://developer.atlassian.com/blog/2015/06/discontinuing-ide-connectors-support/ this blog post] for more details.
  
−
[https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=Mylar&component=Jira&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit  Open task in Bugzilla]
+
== Information for Integrators ==
  
−
== JIRA web service API needs ==
+
The Atlassian update site distributes a feature and plug-in that with the same bundle ids as the Mylyn JIRA Connector (org.eclipse.mylyn.jira_feature) but with a higher version (3.4.0) than the latest available release of the Mylyn JIRA Connector. The stubs do not contain classes or extension points and effectively disable the Mylyn JIRA Connector.
−
* Service to get RPC api version (need to call this before calling anything else) - could be added to the existing getServerInfo service
+
 
−
** We actually need to support RPC plugin versions, not Jira versions.  Currently we just guess the rpc version based on the Jira version
+
Extensions that integrate with the Mylyn JIRA Connector need to specifiy the following version constraints in the manifest:
−
* Adding and removing attachments.
+
 
−
** Attachment names/ids should be present on the issue object
+
Require-Bundle:  org.eclipse.mylyn.jira.core;bundle-version="[3.3.2,3.4.0)",
−
* Retrieving and adding votes.
+
  org.eclipse.mylyn.jira.ui;bundle-version="[3.3.2,3.4.0)"
−
** Number of votes and whether or not the current user has voted should be present on the issue object
+
 
−
* Watching (CC) status of the issue given the current user (should be present on the issue)
+
Features should specify an equivalent version match:
−
* Watch/unwatch an issue during an update by setting/unsetting the watched flag on the issue (allows us to reassign an issue, but continue to watch it with one call)
+
 
−
* Retrieving workflow actions and submitting the corresponding operations (based on an issue type, project and current status)
+
<import feature="org.eclipse.mylyn_feature" version="3.3.2" match="equivalent"/>
−
* Retrieving screen layouts given issue type, project and action (for editing custom fields on workflow transition)
+
 
−
* Submitting query/filter and only getting keys back (not issues+comments).
+
The latest release of the Mylyn JIRA Connector is available from this archive update site: archive.eclipse.org/mylyn/drops/3.3.2/v20100222-0100/extras
−
* Service to get issue summaries (everything but the comments) given a set of issue keys (for populating search results page at a time)
+
−
* Service to get all server configuration at once (Projects/Components/Versions)
+
−
* Service to get server "customization" settings (is voting enabled, attachments allowed, etc...) - currently admin only
+
−
* This is needed to disable operations that are not enabled on the server
+
−
* Service to get all 'meta' information at once (issue types, issue statuses, ProjectCategory, etc) - any configurable objects that apply across projects
+
−
* Project object should say what category it belongs to (if any)
+
−
* Service to search for issues - model this after the core services search method? ie. object based query
+
−
** Allow searching by voting and watch status (I don't think these are currently stored in the GenericValue object, so aren't indexed by Lucene)
+
−
** Allow searches to be saved as named queries
+
−
* Service to search for users - like the issue search, just return IDs and let the caller get the details
+
−
* Service to search for groups
+
−
* Service to get wiki macro details (for rick text editing)
+
−
** Is it a block macro
+
−
** Does it have parameters, if so, what values are possible
+
−
* Custom fields should be available on the Issue object
+
−
* Issue links should be available on the Issue object
+
−
* Service to add/remove issue links (could be done while saving the issue if they are present on that object)
+
−
* Provide all services in wrapped doc/literal format to be WS-I compliant.  Some toolkits such as XFire only support Doc/Literal web services
+

Latest revision as of 01:04, 21 February 2018


Atlassian has ended support for the Atlassian JIRA connector See this blog post for more details.

Information for Integrators

The Atlassian update site distributes a feature and plug-in that with the same bundle ids as the Mylyn JIRA Connector (org.eclipse.mylyn.jira_feature) but with a higher version (3.4.0) than the latest available release of the Mylyn JIRA Connector. The stubs do not contain classes or extension points and effectively disable the Mylyn JIRA Connector.

Extensions that integrate with the Mylyn JIRA Connector need to specifiy the following version constraints in the manifest: 

Require-Bundle:  org.eclipse.mylyn.jira.core;bundle-version="[3.3.2,3.4.0)",
 org.eclipse.mylyn.jira.ui;bundle-version="[3.3.2,3.4.0)"

Features should specify an equivalent version match: 

<import feature="org.eclipse.mylyn_feature" version="3.3.2" match="equivalent"/>

The latest release of the Mylyn JIRA Connector is available from this archive update site: archive.eclipse.org/mylyn/drops/3.3.2/v20100222-0100/extras

Retrieved from "https://wiki.eclipse.org/index.php?title=Mylyn/JIRA_Connector&oldid=423127"

This page was last modified 01:04, 21 February 2018 by Eclipsepedia anonymous user Unnamed Poltroon.

Back to the top