Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to add Impacts to Issue

Sadavanh Chanthakeo-Doll
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 1, 2022

I'm trying to create Issues within my Backlog. One of the requirements is now missing. It won't let me move past Impacts. I was able to make my selection last week. I've tried to add it as an option in Configure Fields but it's not there. 

 

Has anyone had this issue?

1 answer

0 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 1, 2022

Welcome to the Atlassian Community!

What are your "impacts"?  Are they a step in the workflow?  Or a field in the issue create screen?

What does "won't let me move past" mean?  Error messages?

Sadavanh Chanthakeo-Doll
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 2, 2022

Hi and thank you! No, Issues is a required field for our board. For some reason, it is visibly not there when trying to create an issue. It keeps giving me an error message that an Impact is required field. 

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 2, 2022

Ah, I see.  I wasn't sure what your "move past" bit meant, it implied workflow to me (I've been here a while, I default to thinking in Jira-speak)

There are a couple of things this could be.

First, your config - this is unlikely because Jira should do it, but look to the top right of the create screen and look for the configure button - is "impacts" deselected in there?

If it's not that, you will need to talk to your administrators, they have created an inconsistency between two places in the configuration of your project.

1. The "create screen" does not have the impact field on it

2. The "Field configuration" has set the field mandatory

One of those needs to change!

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events