Please be informed that we do not support Next-Gen Project. Please use the standard Jira project type in order to be able to use BigPicture plugin.
Here is a quick instruction which project type to select.
What are warnings?
Warnings are event messages which appear while our plugin is operating. Every time add-on needs intervention from a user or an administrator, it generates a specific warning. Warnings' presence is indicated at plugins header by exclamation triangle on a red field, that replaces BigGantt's or BigPicture's logo icon.
Click it to open Warning Management Dialog.
Warning management dialog displays a warning log which helps us to manage add-on's malfunctioned behavior. Every row of warnings in the log corresponds to a specific type of interaction between the plugin and environment that and contains:
- WARNING - warning message,
- AMOUNT - how many times the warning has occurred,
- ACTION - link to a place where warning can be addressed (optional). Please be aware that action link does not resolve the issue automatically!
Warning table can be sorted by columns: WARNING and/or AMOUNT.
When all warnings are addressed, then warnings log should be cleared with the Clear log button.
To allow Add-on operate properly, all warnings should be resolved! If any doubts contact firstname.lastname@example.org.
How to deal with the Permission Warnings?
Most common permission warnings will concern project screen security. To resolve this type of warnings you must have administrator permissions. BigGantt and BigPicture add-ons may use issue custom fields to store Gantt chart data. Those custom fields are configurable under Gantt configuration screen in Jira Administration → Add-ons.
Go to Add-ons:
Then click on "Task configuration": and check what issue fields BigGantt/BigPicture make use of:
All fields that BigGantt/BigPicture make use of, should be visible and editable on every issue of every project BigGantt/BigPicture program is based on. If fields used by Add-on can not be updated due to project screen security, then following warnings will appear:
In order to resolve this kind of warning you should make the fields editable in given project. Above image shows warnings in TEST21 project. You should alter the project screen security to allow the fields to be edited.
Go to Project's project list:
Find your project and click at project name link:
You should be directed to project page. Select Project settings tab.
Select Screens tab:
Now you should see project screens configuration.Project screen configuration aggregates screen security schemes that apply to specific projects. Screen security schemes may apply to different types of issues.
Click on one of the screen security schemes. You should see a similar screen with message "Project key XYZ - Field 'customfield_10032' cannot be set. It is not on the appropriate screen, or unknown.":
Make sure that screen security schemes of Create issue and Edit issue for all issue types contains fields used by Gantt configuration.
You have 3 ways to obtain it:
- Alter all screen security schemes that the project make use off. This is what we have already described.
- Add fields that BigGantt/BigPicture makes use of to multiple screens in bulk.
- Go to Administration:
- Select Custom fields tab, select one of the fields settings icon, select Screens:
- You should see all screens associated with the field. Select those screens the field should be associated with and click Update.
- Go back to the paragraph b, repeat for all fields used by BigGantt/BigPicture.
- Go to Administration:
- If you have at least one screen defined in such a way, that it allows for update of all fields BigGantt/BigPicture make use of then you can use it as project security scheme.
- Go to project screen settings:
- Go to screen security scheme edition:
- Edit issue operation:
- Select properly defined screen and update.
- Go to point b and repeat for all schemes.
- Go to project screen settings:
Bear in mind that even if after setting up screen security the 'Program warnings' dialog still appears, there is a simple hint on how to check if screen scheme configuration has been properly set.
1) Pick a random Issue from the Project which triggers the error. In the scenario given below we took 'Story2' Issue from the Project which KEY = TEST.
2) Go to Issue Detail Page of this Issue and select 'Where is my field?' option from the 'Admin' drop-down menu.
3) The next step would be seeking for the missing fields. This way you can use Jira's functionality to track down screen schemes misconfiguration.
4) Once all the Project's screens are configured, the only thing remaining is to clear the log. This can be done by simply clicking the 'Clear log' button within the 'Program warnings' dialog.
This action should prevent the 'Program warnings' pop-up window from appearing any further. Please remember that you would need to have Jira Administrator's or equivalent privilege to clear the log.
Also, sometimes you may face the situation when the 'Clear log' button is either not responsive (you were clicking but to no avail) or grayed-out. In this case clearing add-on's cache might help.
This can be done in add-on's 'Technical Info' section within Settings –> Add-ons:
If you still find it too difficult to configure just drop us an e-mail at email@example.com so we could approach your problem a bit faster via short screen sharing session.
Remember to verify screen security configuration every time program creation is filling project with data! We have prepared quick link on program wizard:
Every program (collection of issues) is defined by scope. Program scope can be found in Gantt configuration under Scope tab.
Scope is defined using scope elements like:
- JQL query.
Technically scope is transferred into JQL query executed on behalf of scope context user.
In JIRA lifecycle scope elements may be deleted. Scope elements deletion does not alter program scope definition, this is why it may cause program scope misconfiguration.
If issue of id=271217 is deleted, then for the above program scope configuration a JQL validation error will appear.
The error will be written to warning log, e.g.:
In order to fix the warning, program scope should be fixed.
Other permission warnings may concern project permissions. Verify project permissions if other permission warnings happen: