Issue Management Systems

This page is an attempt to collect information about different issue management systems, what features they provide and how you can interact with them in a head-less way. The purpose is to see if it is possible to create a common API for them. The first consumer of that API would be Maven Changes plugin.

Systems

Name	Product URL
JIRA	http://www.atlassian.com/software/jira

Head-less communication

Name	head-less communication	URL describing the communication
JIRA	RSS 0.9.2	http://www.atlassian.com/software/jira/docs/v3.13/navigatorviews.html

Features

Generic name	Description	Example values
key	A unique non-numeric identifier for this issue	PROJECT-123
id	A unique numeric identifier for this issue	12345
title	[key] summary	[PROJECT-123] It doesn't work
description	A full description of the issue	Long text explaining what it is that doesn't work
summary	A short description of the issue	It doesn't work
link	A URL to the issue	http://jira.company.com/browse/PROJECT-123
type	What kind of issue it is	New Feature
priority	How important it is	Major
status	The current status, in a work-flow context	Open
resolution	How it was solved	Unresolved
assignee	The person who solved the issue	Dennis Lundberg
reporter	The person who reported the issue	Joe User
created	Date and time when the issue was created	Sun, 2 Jan 2011 22:44:54 +0200 (CEST)
updated	Date and time when the issue was last updated	Sun, 2 Jan 2011 22:44:54 +0200 (CEST)
version	The version in which it was fixed	1.2.3
due	Date when the issue was supposed to be solved	Mon, 3 Jan 2011 00:00:00 +0200 (CEST)
votes	The number of people who thinks it should be solved	4

Features per system

Generic name	JIRA
key	key
id	id
title	title
description	description
summary	summary
link	link
type	type
priority	priority
status	status
resolution	resolution
assignee	assignee
reporter	reporter
created	created
updated	updated
version	fixVersion
due	due
votes	votes