Hi, I'd like to create a custom JIRA field, that exists at a project level (not a task/ticket level), so that we can identfy projects by LOCATION when exporting JIRA timelogs. So basically i'd like to see the following scenario happen: * Create Custom Field called LOCATION * Setup a new JIRA project called "PROJECT UK" * Assign Location = United Kingdom to "PROJECT UK" * Setup a new JIRA project called "PROJECT SA" * Assign Location = South Africa to "PROJECT SA" * Export JIRA worklogs and see the LOCATION field populated as either "United Kingdom" or "South Africa" depending on the project. Is this possible? As far as I can tell custom fields can only be assigned against tickets., not projects. Kind regards Mark

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Is it possible to create a Custom Field at a PROJECT level

Mark Hawkins

Hi,

I'd like to create a custom JIRA field, that exists at a project level (not a task/ticket level), so that we can identfy projects by LOCATION when exporting JIRA timelogs. So basically i'd like to see the following scenario happen:

Create Custom Field called LOCATION
Setup a new JIRA project called "PROJECT UK"
Assign Location = United Kingdom to "PROJECT UK"
Setup a new JIRA project called "PROJECT SA"
Assign Location = South Africa to "PROJECT SA"
Export JIRA worklogs and see the LOCATION field populated as either "United Kingdom" or "South Africa" depending on the project.

Is this possible? As far as I can tell custom fields can only be assigned against tickets., not projects.

Kind regards

Mark

Accepted answers

Jack Brickey

maybe i don't understand the UC well enough but why not simply create Location custom field and use different workflows per project allowing you to use a post function to set the field for every issue created? So every "Project UK" issue would have "UK" location and every "Project SA" would have "SA" location, etc?

All comments

Raynard Rhodes

You may be able to use PROJECT CATEGORY for this. If you go under Project Settings > Details, you'll see Project Category. Click on the "i" and it'll take you to the location where you can set the category. Create categories called UK and SA and assign them to specific projects.

I personally haven't done this, but it seems like a good option.

Mark Hawkins

Thanks for the reply. We currently use PROJECT CATEGORY as a "Project Type" field - see here: https://gyazo.com/2dfdf82e9d4b9157cfa44b06f4e5ab5f

But even if we had used Project Category for the location, I don't actually see this field anywhere in the exported data, which is interesting as I would have thought it would be exported.

We currently use TEMPO TIMESHEETS, and we're exporting data from there but I would have expected Project Category to have pulled through.

At the moment we have Location set as a custom field within TEMPO, but our users have to manually select the location each time they log a worklog, which is annoying. The goal here is to define location when setting up the project, so that all worklogs get assigned the correct location automatically.

Hope that makes sense.

Ryan_y7hs9q

@Mark Hawkins ,

There is not a way to add more metadata to the Jira project natively. It appears that there is a plugin available to extend metadata functionality at the project level: : https://marketplace.atlassian.com/apps/42075/metadata-for-jira?hosting=server&tab=overview&_ga=2.230192794.749844219.1555336600-678078101.1547065673.

See here for a similar question: https://community.atlassian.com/t5/Jira-questions/Metadata-at-Project-level/qaq-p/862051.

However, I'm not certain if Tempo will see the custom metadata if you need to push/pull that information into Tempo or how the metadata will get exported. You'll likely want to test this in a staging or test environment to confirm.

I hope that helps.

Jack Brickey

Mark Hawkins

This solution worked.

I did have to reach out to JIRA support, as I was getting an error and they provided additional steps to ensure that the new field is hidden by default on tickets, and set 'behind the scenes' - their response as follows:

If you want to achieve that, you should add that field to a Screen and Make the field hidden on the form from the Field Configuration.

First of all, add that field to the Screens for All the Issue types needed.
Then on the Field Configuration make the new Custom Field set to "hide" by clicking the ellipsis icon
Then attempt your Issue creation again

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

custom-field

jira

cloud

jira-cloud

field