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; } } }

View/Edit Affected Version as Custom Field

Peter Christopher

I want to be able to view/edit the Affected Version/s field in my advanced roadmap plans. It's not there by default, so I added it as a Custom Field. When I selected the field from the list of available fields, is shows as "Supported". That is all good.

However, when I add that custom field to one of the views it does not show any values and the dropdown also does not have any values to select from.

I have done this same thing for other similar dropdown fields without issue.

Am I missing something or is this perhaps a bug with just that field?

Jira Version 8.1.0

Comments

Joseph Chung Yin

@Peter Christopher -

Hi Peter:

The "Affected Version/s" field is pulling and using version values from the Fix Version/s as system default setup. If you create a custom field, the field type has to be either Version Picker (multiple versions) or Version Picker (single version).

Only those two field types can associate the field with your project's version setup. Also, you need to ensure that issues associated with the specific project that the project itself has created versions already. Otherwise, if the project has no version(s) defined, then the custom field dropdown list will be empty.

Hope this helps.

Best, Joseph

Jira/JSM Functional Lead, , Global Infrastructure Applications Team

Viasat Inc.

Peter Christopher

If I understand you correctly, that is not my intention. I am fine with Fix Version/s being used for the Release values in the plan configuration.

My simply goal is to surface Affects Version/s as a field that I can show in the "Fields" when viewing the plan. I am clearly missing a step somewhere (or it's not possible).

Rafael Francisco Garabato Bonino

I am affected by the same problem. I just only want to surface affected version but is not available as a custom field. Was there any solution identified for this problem?

Peter Christopher

I have not found a solution yet

Joseph Chung Yin

@Rafael Francisco Garabato Bonino and @Peter Christopher

After further research (as you may already know), AR plan currently doesn't support custom fields with datatype of versions.

The following custom field types are supported:

checkbox
date picker
user picker (single user)
number
radio button

label
single-choice select
multiple-choice select
single-line text
URL (read-only)

Can you use the Release field to expose your needs for Affects Version/s? The Release field is the Fix Version/s. You have the following options based on my analysis -

1) Try to use the Release field to expose in your plan (remember issues can associate to one or more releases/fix versions. Don't know if it is applicable in your business process.

2) Try to use Component/s or custom fields with the aforementioned datatype above. Meaning that you populate the Component/s or custom fields with the needed "Affects Version/s" values. Afterward expose them in your plan.

3) Create scripted custom fields based on the supported datatype (you will need Script Runner for Jira Add-on) to copy the value populated in Affects Version/s field. Afterward, add the scripted fields to your AR plan.

4) If you do not have Script Runner for Jira add-on, you can customize your WF to use post function calls in your WF transitions to copy the Affects Version/s populated value to custom fields associated with the supported datatype. Afterward, add the custom fields to your AR plan.

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

Peter Christopher

Short answer is I understand those workarounds, but it would be nice if the product supported that field type out of the box.

Longer answer:

I don't want to change Release because that is useful and accurate as-is (the intended product release which corresponds with Fix Version)
We were hoping to avoid doing something like this as it adds extra fields to all the projects and creates duplicate data that isn't necessary except to work around this limitation. Also, adding a field requires a whole process of internal approvals, justification, testing, etc.
same as #2
same as #2

Rafael Francisco Garabato Bonino

Exactly, @Peter Christopher ´s answers is as if I would have given them myself. I just want to add that we use AffectsVersion as a way to label requirements that will be developed during the same release timeframe than the next release, but delivered after it. So for instance, we say we want to release feature A for release Q2, and feature B for release Q3, but development will be started during Q2. So we use fixVersion of Q2 for feature A, and Q3 for feature B, but then AffectedVersion is set to Q2 for feature B.

Joseph Chung Yin

@Rafael Francisco Garabato Bonino and @Peter Christopher -

You are correct that Atlassian should fix this issue. I can only recommend that for you to submit formal support request to Atlassian for the bug fix/enhancement solution.

Best, Joseph

Welcome!

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

Quick Links

Find more posts tagged with

advanced-roadmaps