Although there are awesome extensions to do this, I am looking for a native solution.
How I did it using Jira Automation.
Detailed screenshots that require configuration:
Clone epic and set assignee to User who triggered the event.
Create variable using {{createdIssue}}.
Add an epic link to cloned child issues and set assignee to User who triggered the event.
Related
I would like to exploit the integration between the two tools to be able to automatically create a branch in GitLab for every new Bug or Feature ticket created in Jira.
I would like to know if (i) it is possible; (ii) what is the link between the two tools (I guess the unique ID number assigned by Jira); (iii) assuming the first point is true, what happens to the created branch when I close the Jira issue (e.g. I've mistakenly created a bug fix that was not needed).
I've used Jira in conjunction with GitHub so I'll try my best to help you.
I) This is definitely possible.
II) We used to use the unique ID given to a ticket and include it within in the branch name this creates a link between both tools. Any changes committed on the branch will be shown in JIRA.
III) From experience when this happens the branch will persist and will need to be deleted manually using a console we used to use a .git console and used a delete command.
I also found through a quick google search some documentation on GitLab on integration with JIRA as well as some insight on creating branches.
Doc - https://docs.gitlab.com/ee/user/project/integrations/jira.html
Branch - https://gitlab.com/gitlab-org/gitlab-ce/issues/3886
Hope this helps.
I installed JIRA 6.4. I also Crerated Project and Issue in it. I assigned Issue to some user. Now If Administrator wants to monitor isssue status, he can see progress. But how does the asignee i.e the person working on issue update issue status. Actually I am very new to JIRA. Or is there any other plugin for it
Depending on the workflow you have configured for the project, the assignee should see action buttons on the issue that they can click to progress status; e.g. "Resolve Issue" or "Close Issue". These are known as "Transitions" in the workflow and configure how issues can move between certain states.
If you're also using the JIRA Agile add-on, you can create a "Rapid Board" that allows assignees to drag and drop issues between states to create a "Work in Progress" board.
This is just a starter, it's best to run through the tutorials from Atlassian, they will take into account the various project setups that may apply to you.
Also, if you're just getting up and running with JIRA, it may be advisable to upgrade to JIRA Core 7 (or JIRA Software if you require the extra features) as it has project templates/workflows that will make getting up and running a lot quicker.
We want to create a defect/task in Jira automatically for a failed build in Bamboo. And need to assign this defect to the person who broke the build.
How to do these two things?
Thanks.
There is an open JIRA issue regarding this -- BAM-2537 -- watch it, vote for it - maybe they'll add it to the product.
The comments from Top 5 Reasons Creating JIRA Issues from Bamboo Makes Your Team Awesome-r also discuss what you're after.
Have a look at Atlassian CLI. There's already a good answer on StackOverflow.
Can Bamboo change status of tickets in JIRA
This is not "out of the box" solution, of course, and requires some additional work.
Curently, Jenkins JIRA is polluting the comments in JIRA page, especially with matrix builds.
We had an issue with a couple of user comments and many hudson comments.
Every build, it records the changes.
Any idea to get rid of this issue?
Per Jenkins wiki, user has an option to turn updates on and off in Post-build Actions settings.
To turn off, make sure that there's no check mark set at "Updated relevant JIRA issues"
I have installed Jira and the subversion plugin (with success from what i can tell from the administration panel - subv. plugin installed).
I then add a repository that I have created on the file system, BUT i cannot see an option which will link/connect a new or existing project to a SVN repository. What i want to do is link a project with a repository so I can track commits made to the project (link commits with issues). After some searching i found that this is possible but I cannot figure a way to do it.
Do I need another plugin for that? I have tried googling for the last hours but I cannot find anything related.
regards,
The way SVN-Jira linking works by default is to simply put the issue identifier of the Jira issue in the comment when committing to the SVN repository.
It can be helpful to enable comment editing in the repository, if you have past commits or users who forget to add comments when committing.
Example commit comment:
Fixed problem with login. See issue MYJIRAPROJECT-26 in issue tracker.
There's a service in Jira which scans the SVN repository at regular intervals, and builds a cache of any SVN revisions where an issue identifier appears. Depending on the polling interval, it make take a few minutes for the commit to show up in Jira.
The polling time is controlled by the JIRA Service for the SVN plugin. See Admin, Services.
~Matt
you can enforce that future subversion commits require a jira issue reference for more reliable--than relying on your programmer's word ;)--jira-subversion integration
the jira commit acceptance plugin can be configured to block commits that don't include a valid (defined by subversion-jira project mapping and/or regular expression as appropriate to your situation) jira issue reference in the commit comment
reliable jira-subversion linkage availability allows handy stuff like:
Integration with issue trackers