#Bugzilla update how to
#Bugzilla update update

git/info/grafts file to provide artificial merge points between the two remote repositories. Git branch -track upstream remotes/upstream/master

Create a local git branch to track the upstream/master branch.

Import the upstream Bugzilla git repository.

Import Websites/ from the WebKit repository into a local git-svn repository.

If you have a modern Xcode on macOS, these are already installed.

Subscribe to the mailing list to receive email for security updates and new releases.

If you already have a git-svn repo for Websites/, you can skip to the Setup from git-svn Repository section.

#Bugzilla update how to

This section describes how to set up a merge environment from scratch.

#Bugzilla update update

URLThis page describes a process to update the Bugzilla instance running on .

Then select Create for the Bugzilla v4 API at the top of the page. How to create a Bugzilla version 4.x integrationįor Buzilla version 4.x, go to the INTEGRATIONS tab in your project view, click Add an integration, and select Bugzilla. This adds a state change comment to the Bugzilla bug. The user that is used for the integration must be a member of an “insider group” for this to work. Use this in conjunction with the Product field to narrow the bugs to be imported. ComponentĮnter the name of your Bugzilla Component. Use this in conjunction with the Component field to narrow the bugs to be imported. ProductĮnter the name of your Bugzilla Product. If this field is left blank, all bugs will be shown. The default values are Resolved, Verified, and Closed. This is the comma-separated list of status names that should be excluded from the imported bugs. Note that you must use the secure “https” rather than “http.” Bug “Status” values to exclude This is the URL of your Bugzilla server (e.g., ). You’ll see this when you view a list of integrations. This is the integration’s associated project. How to create a Bugzilla version 5.x integrationįor Buzilla version 5.x, go to the INTEGRATIONS tab in your project view, click Add an integration, and select Bugzilla.

It is possible to move stories that have been created from a supported integration to another project as long as the destination project is set up with an equivalent integration.

To configure integrations for a project, you must be an owner of the project, an account admin, or the owner of the account the project is in.

This integration may work with earlier versions, but we support Bugzilla versions 4.4 and above.

The integration only supports the default Bugzilla statuses as described in the Help for your installed version (e.g., here.

Improving performance in large projects.Configuring ADFS with Tracker for SAML SSO.

Updating your name, email, and initials.

Consultancies - managing client accounts.

Selecting/changing a Tracker subscription plan.

Moving stories or epics between projects.

Tracking big features and themes with epics.

Understanding project and profile time zones.

Setting the iteration start day and project start date.

Moving a project to a different account.

Navigating between projects and Workspaces.