Support for Atlassian Server Products (and apps like BigPicture) has ended in February 2024.
Are you planning a migration to Cloud? Make sure you don't lose your BigPicture data/configurations in the process. Check out this page for information on how to migrate BigPicture's data to Cloud. If you have any questions please email support@appfire.com
Customfield_XYZ cannot be set
Table of contents
When using the Cloud version of our App, you may encounter the following error:
Project Key XXX - customfield_XXXXX: Field 'customfield_XXXXX' cannot be set. It is not on the appropriate screen, or unknown.
To resolve this problem, you must have Jira administrator permissions.
The App is trying to use an issue field and fails because the field is missing from a Jira project screen scheme.
In the example above, the problem concerns:
a Jira project with a key: DP0
a field: customfield_10015
Classic Projects
Find the Field Name Missing from the Screen Scheme
BigGantt and BigPicture may use issue custom fields. Those custom fields are configurable under Apps > Manage your apps.
From the list on the left, access BigPicture/ BigGantt Configuration.
A warning will appear. Click Cancel to access the App configuration.
Go to the General > Fields tab.
If the project in question uses custom mapping settings, check them specifically. As specified in the warning message, the Jira project in question has the following Key: DP0.
Switch to the "Custom mapping" section. Click on the project name or the Edit button to see the settings. The custom field ID will help you quickly locate the field in question. In this case, because customfield_10015 was listed in the warning message, we know the Start date is the field missing from the screen scheme.
Use the Project Key to Find the Project
Click Projects > View all projects.
Enter DP0 in the search box.
Open the project by clicking on its name.
Find the Screen Scheme Associated with the Project
Go to the Project settings page.
Select Screens from the list on the left.
Find the Fields Associated with the Screen
Update the Issue Type Screen Scheme(s)
Click the edit button on the right.
Click the name of the screen.
You will see the list of fields associated with this screen scheme.
Add the missing field (Start date) to the screen scheme.
Once all the issues have been addressed, clear the log by clicking the 'Clear log' button within the 'Program warnings' dialog. Even if issues have been fixed, the dialog box won't disappear until the log has been cleared.
Team-managed Jira projects
Activate the toggle switch on the BigPicture configuration > General > Fields page. The App will run without problems, even though the fields have not been added to the issue types.
Keep in mind that the use of team-managed Jira projects is not recommended.
Keep in mind more than one field can be causing an issue.
Check the Technical Configuration of the App
BigGantt and BigPicture may use issue custom fields. Those custom fields are configurable under Apps > Manage your apps.
From the list on the left, access BigPicture/ BigGantt Configuration.
A warning will appear. Click Cancel to access the App configuration.
Go to the General > Fields tab.
If the project in question uses custom mapping settings, check them specifically. As specified in the warning message, the Jira project in question has the following Key: NXTGN2022.
Switch to the "Custom mapping" section. Click on the project name or the Edit button to see the settings. Scroll down to find the toggle switch. Make sure to hit Save.