Page Comparison

1. project: The project's identifier in Jira

Pretty prints, to stdout, all the issues for a given project name, in order of creation descending.

Could redirect output to save in file.

1. project: The identifier of the project to add the issue to.
2. summary: Headline of the issue to be created. Put in quotation marks if it contains spaces.
3. desc: Description of the issue to be created.
4. issuetype: How the issue should be categorized. Examples are bug, task, feature, subtask,...
5. priority: Number from 1-5 where 1 is a Blocker and 5 is Trivial.

 --assignee: The username of the requested assignee, if one should be immediately assigned.

--parent: The identifier of the parent issue. Only required if you create a subtask.

Browsing and Issue Creation Permissions

--conffile: Absolute path to the file where the config values should be saved/overwritten. If it doesn't exist, attempt to create it there.

Any of username, password, oAuthToken, consumerKey, consumerSecret, oAuthSecretToken, authMethod, privateKeyLocation, baseurl that should be saved in the config file

--consumerkey: The name of the OAuth public key as configured on the Jira Server. Specify to use a different one than the config file has.

--consumersecret: The OAuth secret as configured on the Jira Server. Specify to use a different one than the config file has.

--pkeyloc: Path to the private to be used for the creation of this token.

Create an OAuth token.

Important:

OAuth Consumer must have been configured server-side by an Administrator. 
A Tutorial on how to configure that can be found on the official Atlassian Jira Documentation:
https://developer.atlassian.com/server/jira/platform/oauth/
(Only Step 1 is relevant, Step 2 and 3 are handled by JiraClient)

Consumer secret and key already configured on Jira.

Private Key used must correspond to configured public key.