I spent some time in both JIRA website and here, but still couldn't figure out. I have background from ClearCase ClearQuest and RTC. e.g. in CCCQ integration, when a developer check-out a file, he can select a task/bug from CQ due to the integration.
I installed JIRA and Subvertion, and JIRA Subversion plugin. Now couldn't figure out how to achieve the same I do with CCCQ integration.
Please give me a step-by-step instructions. Thanks.
Jirong
Here you go, from the Atlassian documentation: https://confluence.atlassian.com/display/JIRA/Integrating+JIRA+with+Subversion
Related
im trying to setup some projects in jira, we have existing bitbucket repos. Our jira projects have issues we have put in, is it possible to view these jira issues in bitbucket
You can link JIRA to BitBucket by following this tutorial: Linking Bitbucket and GitHub accounts to JIRA. This uses the JIRA DVCS Connector add-on which I believe is a free download from the Atlassian Marketplace.
Branches, pull requests and commit messages can reference JIRA issues. I'm not sure whether you can link existing branches etc though unless they reference the issue in JIRA directly.
I am trying to come up with a custom plugin for JIRA. The custom plugin supports git notes feature in JIRA dashboard.
My question is, does commercial JIRA support a custom JIRA plugin?
And are any tutorials/best practices for developing custom JIRA plugin?
does commercial jira support custom jira plugin?
Yes. You can write your plugin and upload it in the "Manage Add-ons" section of your admin area.
are any tutorials/best practices for developing custom jira plugin?
Yes. Take a look at the JIRA Plugin Guide (the link is broken at the moment of this edit, this link appears to replace the broken one).
You may also investigate Atlassian Marketplace in order to search any specific plugin that develop by other companies.
Since various plugins had already been developed, those are being leaded to you during development of the plugin.
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.
We are happy with JIRA and there is no willingness to move away from it. At present we have JIRA integrated well with Perforce. However we are considering moving to Kiln.
Losing the integration with JIRA would be a blocker.
Perforce not Proforce, right? Kiln has an API that could be used to integrate with JIRA, but I would also consider using Fisheye (from Atlassian) to interact directly with the Mercurial repositories used by Kiln. You could also use the JIRA Mercurial plugin that I wrote to interact with those repositories if you didn't want Fisheye for some reason.
This is an area that I know Atlassian are interested in finding out what people want. If you want to drop me a note about this I can forward it to their Dev Tools group.
Since Kiln uses Mercurial under the hood, you might also want to consider Atlassian's BitBucket, which is a hosted Mercurial repository.
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