Error using Create Multiple Subtasks plugin

Salonica P

I get an error when I use "estimate" even with the example syntax in the documentation.

Does the Create Multiple Subtasks plugin have a prerequisite setup?

Sample syntax from the documentation

#Task 1 example/
#Task 2 example/description:"description"
#Task 3 example/dueDate:"2020-10-01"/estimate:"1d 3h 30m"

Error:

Task 3 example

dueDate:"2020-10-01"/estimate:"1d 3h 30m"

Field 'duedate' cannot be set. It is not on the appropriate screen, or unknown. Field 'timetracking' cannot be set. It is not on the appropriate screen, or unknown.

Earl McCutcheon

Hello @Salonica P ,

Thanks for reaching out, and first just to verify the app you are using, are using app 'Create Multiple Subtasks' by the vendor Eclipse?  Or a different app?

Regardless of the app the error you are running into:

Field '{fieldName}' cannot be set. It is not on the appropriate screen, or unknown.

Is generally triggered while creating an issue if either the field is missing from the project create issue screen or the field requires additional permissions from the user adding the value to the field.

First, check the project settings and verify that the 'duedate' and the 'timetracking' fields have been added to the create issue screen and that the fields are visible (not hidden) under the Field Configuration.

Next, as permissions are concerned both fields require 'Edit Issue' permissions and the duedate field requires  'Schedule issue' Permissions, and the 'time tracking' field requires 'Work On Issues' permissions allowing a user to log work against an issue or create a worklog entry. 

However there are a few issues you may run into here first as this is tied to an add-on app adding the data, I am not sure if the app is passing the permissions of the user triggering the create action or if it is using the Project Role 'atlassian-addons-project-access' to create the issue on behalf of the user.  So check the Project permissions and verify if the app has the appropriate permissions set, and if not it would be the user triggering the action requiring the permissions.

The next issue here is that this thread is flagged as a Cloud Free plan, and the ability to modify permissions is locked on the free plans to add a barrier of entry to prevent abuse on the system from bots and malicious actors looking to use the system maliciously,  with additional details on the permission restrictions covered in "Permissions and issue-level security in Free plans" :

 Project permissions, roles, and issue-level security aren't configurable when you're on the Free plan. To take advantage of Jira's powerful project permission management features, upgrade your plan.

So if you are on a Free plan you would need to upgrade the instance to enable a trial of the full version of the application to be able to modify the permissions,  This can be done by selecting the Admin Gear icon in the upper right of the instance and navigating to Billing > Manage Subscriptions, and selecting the "Change" hyperlink next to the 'Free Plan' indicator for Jira, and set the trial to either "Standard" or "premium" "additional details can be seen here" 

If you have already used the free trial period and it has expired, you will need to reach out to our customer Advocates team through a support request under "Billing and Licensing" at https://support.atlassian.com/contact to request a trial extension, or purchase a license on the standard plan to unlock the ability to change permissions on the instance.

Regards,
Earl