Jipcreate Examples

On this page you will find a list of examples of things that a Jipcreate user might want to do. It should be noted that this is not a complete list, but will probably list the use cases that are most commonly used. Likewise each and every combination of keywords that can be specified in the yaml file are not listed here. But you can of course add/remove keywords to set values in the storey created, or remove to use the default value in the story.

Create issue

I want to create a story

$ jipcreate -f /path/to/file.yaml

Fields that can be found in the yaml file are the following for a ‘Story’ or ‘Ticket’. This is an example yaml file.

- IssueType: Story
  Project: LKQ
  Summary: Make LKFT work in tuxtest
  Description: |-
    Some text can be written here.
  AssigneeEmail: firstname.surname@linaro.org
  OriginalEstimate: 5h|5d|5w
  Share Visibility: [donald.duck@linaro.org,micky.mouse@linaro.org]
  Sprint: sprint name

Fields that can be found in the yaml file are the following for a ‘Epic’. This is an example yaml file.

- IssueType: Epic
  Project: LKQ
  Summary: Testing Epic shared visibility
  Epic Name: Different Testing Epic shared visibility
  Description: |-
    Some text can be written here.
  AssigneeEmail: firstname.surname@linaro.org
  Share Visibility: [donald.duck@linaro.org,micky.mouse@linaro.org]
  Due date: 2023-06-31

NOTE: Required fields depends on what is configured in your JIRA instance.

Testing / development

I want to do a dry-run

$ jipcreate --dry-run

With --dry-run you can query the real Jira instance without risking to make any updates. I.e., this can be used to see what will be sent to the server.

I want to see more debugging text from Jipdate

$ jipcreate -v