Versions Compared

Old Version 3

changes.mady.by.user Gabriella Barreto Murrell

Saved on

compared with

New Version Current

changes.mady.by.user Lucas Cirelli Lopes

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

When associating custom fields to project, it’s important essential to remember that any changes made to their set of options can impact other projects depending on your configuration. Below, we listed the best practices when project mapping your custom fields as to reduce any side effects on other projects that might also be using them and to avoid overcharging your project administrator:

(tick) Do's

(error) Don'ts

Map custom fields that might need new options frequently.

Map custom fields that have a fixed set of options and should not be freely edited.

Create unique contexts for fields that are used by multiple projects.

Keep all of your custom fields

on global context.

Associate only custom fields you’re sure your team will use.

Add unnecessary custom fields that aren’t used in your project or that won’t need to be managed by your project administrator.

in single a global context when they may be used by multiple projects

Map custom fields to projects that requires frequent upgrades.

Map custom fields that should have a fixed set of options or should only be managed by a Jira Admin.

Map relevant custom fields.

Map custom fields that won’t be used in your project.

NAVIGATE THROUGH OUR DOCUMENTATION:

← ACCESSING A PROJECT THROUGH THE ADMIN PAGE | OPTION MANAGEMENT →