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

Can't create an issue through the side bar of Bonfire

Chelmer

I'm using 1.6.2 bonfire plugin. Tried to create an issue through the side bar of bonfire, however it complaints a mandatory field was

needed. In fact the mandatory field was not displaied in the side bar and therefore i'm not possible to create any issue through it.

Is there any way we can configure the mandatory field enable in the sidebar?

Accepted answers

gdavidson

Bonfire uses the Create Issue screen scheme to determine which fields to display for a given Project and Issue Type.
What it can't handle at the moment is custom fields that come from other plugins.

Is your mandatory field provided by JIRA itself or another plugin?

All comments

gdavidson

Bonfire uses the Create Issue screen scheme to determine which fields to display for a given Project and Issue Type.
What it can't handle at the moment is custom fields that come from other plugins.

Is your mandatory field provided by JIRA itself or another plugin?

Chelmer

That field is coming from the project partner, Will it be the problem?

Chelmer

Any plan on coming release will cater the problem of mandatory fields that come from the other plugins?

gdavidson

The issue tracking this problem is at https://jira.atlassian.com/browse/BON-676

The main problem with it is the potential of running untrusted HTML code in the privileged execution environment of a browser extension.
We are looking into solutions though.

Andy Robertson

Can we have an update on this issue please - we have bought Bonfire licences which we cannot use until this problem is resolved -as there does not appear to be a work around. We cannot get the mandatory fields displayed to set them, and we cannot set a new screen scheme for Bonfire to use to avoid it.

edwin

At this stage, we're still looking into what we can do about this particular issue.

Which field are you having this issue with (or which plugin it's coming from)?

Andy Robertson

Its the DB Values Plugin. It is a mandatory field in our implementation as we use it to lookup and set the time/cost code for each JIRA against our time recording system. IS there a mechanism to "park" our bonfile licence? - as it stands at the moment we have bought something we cant use, and if you dont provide a solution will never be able to use.

Welcome!

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

Quick Links

Find more posts tagged with

jira

capture-for-jira