Degraded performance Customers may experience intermittent errors using Community search. Our platform vendor is investigating.
We use Bamboo 5.3 and Jira 6.0
Is there a way to get all the connected Issues to a build plan (not only for every single build extra)?? Similar to the release funktionality.
We have a release and branched in the Sourcecode
We work on a new release but we do some bugfixing on the branch.
The Issues for a Bugfix belong to both versions (I know this is not perfect ...)
Now i would like to have a overview of ALL issues related to an branch. (or the branched build plan)
You may have to pull the information from your repository. (since that's how Bamboo knows an issue is related to a build it should be there). If you're using SVN you can do an query on the logfiles for the branch (limit by revision if you like).
We use something like this (substitute the dollar variables with actual values for your purposes - this was written for perl complete with authentication stuff a simple "svn log" will get you the basics from the command line):
`svn log -v -r $rev1:$rev2 $branchURL --username $svn_user --password $svn_password --no-auth-cache --non-interactive --trust-server-cert --config-option servers:global:http-auth-types=BASIC`;
This gives output with the log contents including revision, user, date, time, files, and comments.
The comments should contain the jira ticket numbers.
If you remove the -v you just get the revision info and the comments (no files listed)
You can filter it further using regular expressions in a script.
As far as I know all the JIRA details associated with bamboo is tied to the individual builds and not accessible for a plan.
For example this:.../rest/api/latest/result/PRJ-PLAN.json will get you a list of builds which (if you were really clever with scripting and regex) could be used with .../rest/api/latest/result/PRJ-PLAN-BLD.json?expand=jiraIssues to get the individual issues for each build. Again extracting them from all the other stuff that is delivered in that result.
Thanks for the response but this i know already.
I would like to get an overview of "ALL" ticktes related to a plan/branch With the solution you descrive I have to manually click through all tickets/builds an copy the Jira numbers :-(
As mentioned above, a report like the "Release Notes" report would be nice
Subversion ALM supports this.
You can make a query on JIRA by using the supported svnItem JQL function.
issue in svnItem(“/foo/”,””,1)
it would return all the issues having commits in the foo branch and all its subdirectories.
You might also want to filter by commit date
issue in svnCommitDateRange (1,”2014-01-15”, "2014-01-31")
it would return all the issues having commits between both dates (from - to)
And you might also want to filter by the BUG issue type.
So the final resould would be:
type="BUG" and issue in svnCommitDateRange (1,”2014-01-15”, "2014-01-31") and issue in svnItem(“/foo/”,””,1)
In In fact, all the registered Subversion repositories are fully indexed by Subversion ALM and you can filter by any Suversion attribute (revision numbers, authors and many more).
ThPlease, read the user guide in order to get more accurated details about the supported JQL functions and how to use them.
Hope this helps.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs