I have two Jira instances (both are Jira Cloud) and the same project in both.
Historically one Jira is used by dev team and second Jira is used by ops.
However, some dev tasks have to be considered by ops team.
So the question: is it possible to sync issues from one Jira to other Jira?
Yes, it is possible to sync issues from one Jira to another, however, this will require you to install additional add-ons to your Jira instances.
In the marketplace you have several available solutions:
Backbone Issue Sync for Jira
Exalate Jira Issue Sync & more
Issue SYNC - Synchronization for Jira
You can trial all of them and pick one that suits you the most. Or in extreme case, if you have some programming skills you could develop such add-on yourself, however, if you include maintenance and hosting costs it's probably cheaper to buys an existing solution.
I'm sure you are aware that you don't have that much flexibility in Cloud. However, check if Backbone Issue Sync plugin can help you or not. In Server it's possible to do it via Issue Sync Plugin.
Related
Is there a way to automate backups for my Jira Cloud site on a daily basis including pulling all the data and attachments?
Atlassian provides option to import-export xml however that cannot be automated as far as I know. Your next best bet to automate it by yourself would be Jira developer APIs (https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/).
Using APIs you can pull data to a greater extent. However it may not be as intuitive as you may want or how it used to be on the on-prem version of Jira server (DB backups). However you may want to plan the efforts & cost for the script maintenance, cataloging the downloaded data and maintaining the data for long term. You can find some details in this thread - JIRA with Python
Alternatively you may want to go for 3rd party apps in Atlassian marketplace which supports automatic/scheduled backups of Issues & Configuration, granular & full project restores, long term storage and secure offsite storage.
Disclaimer - I work at Revyz, we have developed a Jira app which solves this exact problem. We backup & restore Atlassian Jira along with other features as mentioned above. You may want to take a look at https://www.revyz.io/ &
https://marketplace.atlassian.com/apps/1228694/revyz-backup-restore?hosting=cloud&tab=overview
We are planning to implement jenkins for the whole organization. We want to go with single jenkins instance that will be used by many teams with Slave architecture. I want to know if there are any best practices for Plugin management. Since teams would request for installing different plugin, how can i manage these plugsin installation.
Thanks in advance for all your help
I would install Docker on all agent machines and instruct teams to make use of Docker containers in their Pipelines as much as possible. Thereby you forego the need of installing different programming languages and plugins on all your agents.
For plugins that really have to be added to Jenkins, I'd set up a test instance of your Jenkins server, to try out the plugin, and see whether it clashes with existing plugins. Try to keep the number of plugins low, suggest people to only use quality plugins that get recent upgrades, and remove plugins when you no longer need them.
One issue you will encounter is Jenkins has no (as far as I can find) authorization strategy for plugins. Basically, all plugins are available to everyone. Thia may be an issue if teams have different and contraindicated requirements (eg: a team not allowed to use ssh or HTTP requests). If you have a homogeneous approach to SW development, code, infra, tools, etc, then it becomes a matter of scale only..
In a large org, you also may have issues with a single Jenkins merely finding maintenance windows. It also creates a single point of failure.Are you OK w/that or need H/A?
You may benfit from several masters (per business unit or product) and use JCasC to manage common configurations overview, plugin to make your life easier.
Can someone tell me please if is a good idea to use TFS as ticket manager for end users and in the same time as backlog for team developpers?
Not totally sure which kind of ticket manage system you are referring. For tickets, if you mean the ones raised by the end users of an organization whenever they encounter an event that interrupts their workflow.
Then seems you are looking for a helpdesk ticketing system, acts as a documentation of a particular problem, its current status, and other associated information. These tickets are routed to a ticketing software where they are categorized, prioritized, and assigned to different agents according to the organizational norms.
The agents then analyze these tickets and suggest appropriate fixes or workarounds and resolve the issue. As a central repository of all these tickets, an IT Ticketing Software helps in providing the context of the issue history and its resolution.
Then to be honest, this is not what TFS should do. You may have to look for some other system to handle this.
TFS provides integrated tools to support collaborative software development, including Git repositories, continuous integration and continuous deployment (CI/CD), and interactive Kanban boards.
You could also collect bug/feature request and related info from end users, then track them in TFS.
But it's not suggest to let them directly access your TFS system and fire work items by themselves. Cause you need to assign them license and corresponding permission.
TFS fully supports bug tracking and traceability though the code that was changes.
Create your product backlog
The out of the box bug work item is specifically designed to work with the test tools and the planning tools. Besides, you could also use them and add a few customization to meet your requirements.
If you want to use the TFS for the ticketing system. you need create task as a bug /Task in the child link for that particular backlog item or feature. Each task / Bug has to be tracked based on the sprint.
We are using Jira to manage the flow of development of a single application in a Scrum development team.
We want to extend the usage of Jira to include the other applications and micro-services on which the main application relies.
They run with the same development team and monthly release cycle, so we'd like to share the Versions and Epics, having them affect multiple services.
We use Bamboo and Bitbucket and would like to make sure that the requirements for making a particular release is clear in Jira (tracking the links between the stories, software versions and services that need to be released).
If find it hard to see clear advice from Atlassian that points to a particular design, though suspect that components give us what we need.
Has anyone else implemented something similar.
Are components the way forward? Or is something more bespoke / a plug-in a better route?
My company are imposing Jira and Zephyr on us for defect tracking and test management. We're quite happily using TFS 2008 for both these jobs at the moment, but management have never let the fact that something isn't broken stop them from trying to fix it.
Are there any tools/plug-ins that will allow us to synchronise between the remotely hosted repositories and our in-house TFS server?
Probably too late, but the company might want to look at the new features for bug tracking and manual tests coming in the 2010 release. Nice as Jira is, I doubt it will integrate well with the historical debugger and the ability to include a video of the test, as well as information on the test environment, and have it all be part of the work item.