Application access rules are an Atlassian feature that allows you to restrict and control access to specific user-generated content for applications. Adding an application access rule can affect applications that have previously used data in a specific space. Blocking a specific project for Worklogs may result in incomplete data deleted by our application
In response to this, we try to inform the user whenever Worklogs learns that any data for reports is blocked or restricted by the organization.
If you want to view all the necessary data for your report, you should contact the Jira administrator and ask to unlock the requested projects for the Worklogs application.
In the Worklogs interface, you can check for the risk of incomplete data in several places:
Your currently saved reports
Whenever You would load a saved report Worklogs will check if any content is blocked and displey Two flags in user interface:
Blue flag with information that data may be incomplete. It can be dismissed but will appear whenever You will load a report with blocked content. (screen)
pop-up info flag informing You that our app can’t access data from blocked project
On Worklog’s “Manage Worklogs Reports” page all reports that contains data from blocked project will have lavel “Blocked project” next to it.
...
When creating a new Worklogs report:
Whenever you want to create a new report and select a project or a saved filter from the selector, all items blocked by the administrator will be disabled and you will see a "blocked" label next to them. You will see them at the end of the selection list.
...
When logging time in an application.
When you want to log time directly via “Log time” button, you will see an embedded message on the time log modal screen that the results for the selected data may be incomplete - this is due to one or more projects have been blocked for the application.
Note that whenever you try to enter an issue assigned to a blocked project, Worklogs will not display it in the list.