Issue Properties

Added by Tom Chiverton, last edited by Tom Chiverton on Jun 22, 2005  (view change)

A Jira Issue (as returned from JiraCreateSearch) has the following properties, as returned from .getAllKeys():

  created, summary, component, workflowId, timeoriginalestimate, fixfor, 
type, timespent, environment, resolution, status, updated, timeestimate, id, key, duedate, 
description, project, reporter, security, votes, assignee, priority

For example, you can inspect these with .getAllFields():

  created=2004-06-15 10:01:35.0, summary=Web site must display events as occur, 
timeoriginalestimate=null, workflowId=51610, component=null, fixfor=null, type=2, 
timespent=null, environment=null, status=5, resolution=1, updated=2005-01-25 11:42:07.0, 
id=41616, timeestimate=null, key=CEO-415, description=null, duedate=2005-01-25 00:00:00.0, 
reporter=tchiverton, project=10000, security=null, votes=0, assignee=tchiverton, priority=3

getAllFields() returns a Java Map, so you can use

 
Map myIssue = issue.getAllFields();
log.debug("check issue "+myIssue.get("key")+" res= "+myIssue.get("resolution"));

Issues have a change history, see JiraIssueChangeHistory.

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Comments (2)

 

  1. Jul 01, 2005

    Anonymous says:

    What I cant figure out is this... When an issue is resolved, the fixfor stays 'n...

    What I cant figure out is this... When an issue is resolved, the fixfor stays 'null' even though the issue shows a fix version? Where is the issue fixfor stored?

  2. Jul 04, 2005

    Anonymous says:

    You don't have to (in the default workflow) set a fixfor version in order to res...

    You don't have to (in the default workflow) set a fixfor version in order to resolve an issue. FixFor appears in getAllFields() above.

    A better place for questions would be the Jira mailing lists.