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

Use of any JIRA field in a template #15

Open
switchtrue opened this issue Oct 3, 2013 · 0 comments
Open

Use of any JIRA field in a template #15

switchtrue opened this issue Oct 3, 2013 · 0 comments
Assignees

Comments

@switchtrue
Copy link
Owner

Currently the JIRAChangelogBuilder requires a command line argument of "--changelog-description-field " to be provided in order to specify field name in JIRA that provide the issue deescription.

Instead it would be good if you could just use any field name in the template and the changelog builder would fetch the appropriate fields from JIRA.

for example:
{{ summary }}
{{ fixVersion }}
{{ changelogdescription }}
{{ epiclink }}

There would have to be a deterministic policy on how tag names are related to field names (maybe case-insensitive and strip spaces?).

As this will involve the parsing of the templates to determine the field names it would also be good to introduce special place holders that can be replaced with environment variables, for example:

{{ $(SOME_ENV_VAR) }}

See if there is any functionality similar to this already in mustache (my gut feeling is no) and identify the "best way" to name the variables.

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

No branches or pull requests

2 participants