Hot answers tagged

6

I don't think you will be able to get far without any plugins. What you can take a look at is the Default Values for 'Create Issue' screen plugin. We were using it in the past, however gave up because defaults could be set only per issue type, and no other conditions. I was in contact with the supplier, though, and they confirmed that defaults per user and ...


2

You can use the rich jira rest API for this kind of automation work. Jira API provides mechanism to update logged hours using PUT /rest/api/2/issue/{issueIdOrKey}/worklog/{id} You can use this rest API endpoint to update the corresponding issue with the difference of first commit timestamp and first successful CD. Find more about it here.


1

The answer will vary depend on the CI/CD tooling you are using. If you are planning on using Atlassian's CI/CD tool Bamboo, you could use the Bamboo variable ${bamboo.buildNumber} which ties the build number of Bamboo to your version number. You can have a task that will adjust the version based on this variable. Bamboo integrates with Jira so that you ...


1

I think this link on the Atlassian Community forum may be what you're trying to do.


1

You normally would access environment variables using the following syntax: env.MY_ISSUE_ID Typically you'll see the following in practice regarding envvars: pipeline { agent any environment { MY_ISSUE_ID = 'PROJECT-1234' } stages { stage('Build') { steps { echo env.MY_ISSUE_ID } } } } or node{ stage('Build') ...


Only top voted, non community-wiki answers of a minimum length are eligible