Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: removed wrong explanation, caused by misunderstanding

Scheduled Issues after creation are private by default. Only the Creator and Jira Administrators can: edit, delete, share or manually execute Scheduled Issue. Manage Access option allows to grant executeedit and delete permissions to each Scheduled Issue individually. Only the sharing permission (managing access) is kept for Creator and Jira Administrators

...

(warning)  Here, it's crucial to remember, that a user with whom you've shared an issue won't be be able to see anything (and in general won't be able to access Scheduled Issues table listing) if he, or she had not been granted with proper Scheduled Issues Table access permission, by a user with Jira administrator rank. This can be done, as described in here. Moreover, please bear in mind that if i.e. you tick only to share scheduled issue solely with a project role (i.e. like presented above "Administrators"), but not with particular users (i.e. an individual listed as "user1" above) who are members in that Jira project role, then any other user who has not been added individually in "Single Users" box on "Share Scheduled Issue" screen, but is added into this role won't be able to access such issue nor see it in Scheduled Issues table, despite sharing it with ticked project role.

After granting an additional user, with an access to Scheduled Issue table and sharing an issue(s) with him/her, after such user logs in and accesses "Scheduled Issues", visible and accessible issues to such person are only those, with which an original author of a scheduled ones shared with. This is illustrated on the below graphic:

...

Info
titlePlease be advised

(green star) If you want any of your users to be able to use TSP add-on, then you need to first grant him or her with an access via this method. If it won't be done, then such user will be greeted with an "You have no rights to access this Scheduled Issue!" error when trying to do so.

...