Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add documentation for automated edits to the README #415

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

darthwalsh
Copy link

I was trying to automate editing issues, but the README doesn't contain much information for that.
Mention --noedit and --override, and how to customize additional fields.

I was trying to automate editing issues, but the README doesn't contain much information for that.
Mention --noedit and --override, and how to customize additional fields.
To automate editing, use the `--noedit` to skip opening the editor, and pass `--override` fields as defined in `~/.jira.d/templates/edit`:

```
jira edit GOJIRA-321 --noedit --override priority=P0
Copy link

@dkirrane dkirrane May 14, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@darthwalsh How do you override nested/arrays fields? e.g. if you wanted to add Component2 below to the jira

fields:

  components:
    - name: Component1
    - name: Component2

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure! If you open ~/.jira.d/templates/edit there's some complicated templating logic that looks like it merges together .overrides.components with existing .fields.components? But you'd have to try to be sure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants