We have a JIRA instance installed on our side and our client is using that. Now client have purchased license of JIRA on Demand and want us to migrate their project from our JIRA to their.
Is there a way to achieve that?
Thanks in advance
Kaushik
Check out Altasian Splitting+a JIRA instance page:
Occasionally an organisation may need to split its existing JIRA instance into two separate instances. For example, there might be a requirement to have some particular projects in one JIRA instance, and other projects in a second instance.
Basicly, It's done by backing up the project and restoring it on the new server.
You will find a nice tutorial here:
http://www.jusuchyne.com/codingforme/2012/12/jira-migrating-certain-projects-from-instance/
As described here, there is a Plugin in the Atlassian Marketplace, that lets you copy the configuration: https://marketplace.atlassian.com/plugins/com.awnaba.projectconfigurator.projectconfigurator
Related
We are currently using an on premise TFS 2018 installation and there are a couple of custom applications that use the Microsoft.TeamFoundationServer.ExtendedClient in order to communicate with TFS. Now since some assemblies in the extended client are going to be deprecated (link) and a move to Azure DevOps services is a possibility I have started checking the replacement (link)
In our current implementation we are using global lists and extendedClient WorkItemStore had the ExportGlobalLists/ImportGlobalLists methods that were handy
The problem is that I cannot find an equivalent method in the new client
is witadmin the only option?
I have found this in the REST API (link) but it doesn't seem to work for on-premise so I could test it out
Any ideas would be welcome
As far as I know, there is no concept of a global list any more in Azure DevOps Services. If you want to customize the fields, it is usually defining the available list on the field.
We are utilizing the lists on-premise Azure DevOps Server 2019, but only ever interact to get them from witadmin.
According the comment in this case:
https://developercommunity.visualstudio.com/content/problem/312980/cannot-edit-existing-global-lists.html?childToView=338672#comment-338672
Global lists are now part of a specific work item. To edit the list
you should 1) export the process 2) look into the xml for the work
items. Global lists are usually added to the bug or task wit 3) make
the global list changes in the xml 4) zip up the process and import
back into Azure DevOps.
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.
We are working with an offshore development team, I need to send them on a daily basis the list of available bugs and work items from local TFS. I could not find any ready component that would help with exporting the bugs details along with history comments, and attachments.
The excel sheet thing, helps if you want to send it to some one who also has access to the TFS server.
Any clue?
Thanks for the #Daniel and #Cece for your help guys.
I created a solution using .NET TFS assemblies, to help me with this task. The tool connects to TFS and allows you to choose one of your saved queries. It will then export all the bugs / work items information into a folder as HTML, and it will include the attachments and comments on bug if any. It also creates a nice index page.
In case this helps any one, here is the link to download release one excutables from codeplex
https://tfsworkitemsexporter.codeplex.com/
please also feel free to copy the code and edit as you like
You would need to use TFS API to get the attachments and history. Check the REST API:
https://XXX.visualstudio.com/DefaultCollection/_apis/wit/workitems?ids=xx&$expand=all&api-version=1.0
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.
I'd like to know if there is some way to make a checkin on a TFS server associated to a Work Item that's on another.
Currently some of our developers use a TFS that's hosted offshore containing the source code and we need to install another TFS locally to use Work Items as a project management tool and for the rest of our developers.
Beeing able to associate the two (work items + checkins) would be nice but I presume it's not possible.
Thanks
Apparently it's not possible: http://social.msdn.microsoft.com/Forums/en-US/tfsgeneral/thread/d3ddf813-dc13-48a2-808e-7887ddc4d9b1