Set Default Access

[Jens Kisters]

Hello,

we have a large number of tasks that only the owner can edit. Now a second user should get acess to the tasks and be able to edit them.

I am aware you can bulk-change the access, but i cant find a way to set the default access rights, can you help me?

kind regards Jens

[Dominik M.]

Dear Jens,

Full access rights to use The Scheduler add-on can be set, following this manual - https://psc-software.atlassian.net/wiki/spaces/SCHED/pages/2571931

After setting it, you can grant access to particular issues, by following those steps - https://psc-software.atlassian.net/wiki/spaces/SCHED/pages/2528622/Manage+Scheduled+Issue+Access+5.x

To do it in bulk, please refer to - https://psc-software.atlassian.net/wiki/spaces/SCHED/pages/2527995

I hope this clarifies your query. If not, then I look forward to hearing from you with more details (screenshots appreciated).

Many thanks, Dominik

[Jens Kisters]

Hi Dominik,

The access is configured like this:

But when i create an schedule and manage access there the access is created like this:

How can i make access rights be set automatically on a newly created issue?

cheers Jens

[Dominik M.]

Hi again,

I've checked and I see that there's a rule - by default, scheduled issues of its creators are not accessible for other people. The only way to change it, is by granting them access to it.

In your case, if you want to have a template with a scheduled issue with particular users/groups/roles already filled in, I recommend to create a new scheduled issue (or use a one with proper share settings already set, just like presented on your first screesnhot) with it and then instead creating another new scheduled issue, you can simply use "Clone" function. By doing that, yours sharing settings of a scheduled issue will be replicated and you wouldn't need to fill it in manually again.

Cloning procedure - https://psc-software.atlassian.net/wiki/spaces/SCHED/pages/2528140/Cloning+Scheduled+Issue+5.x

Regards, Dominik

[Jens Kisters]

Thanks, we will try this workaround. Can you make a suggestion from this issue?

Happy New Year Jens

[Dominik M.]

Dear Jens,

I recommend to create a new shceduled issue and name it properly e.g. "Template for future SI with proper sharing rights" - please fill only those fields that are to be static, as the rest is to be done by another person to whom you are to grant an access with. Required fields (i.e. "summary") that in future must be changed, can be named as e.g. "Please change summary".

Now you have to make as many clones of such template, as required by your side.

After that, all cloned templates can be granted with the same accesses and editon rights, by following those steps: https://psc-software.atlassian.net/wiki/spaces/SCHED/pages/2527995/Bulk+Share+of+Scheduled+Issues+5.x

Alternatively you may only create one template with required fields filled and desired access/edition rights granted for other people directly after creating it. Then, you can clone it when needed, or make in advance, multiple clones to be stored for future usage.

I hope those workarounds can help.

many thanks, Dominik

[Łukasz Modzelewski]

Hi Jens,

Just wanted to let you know, I have added this to our Roadmap: https://trello.com/c/9k5oG5LH/14-ability-to-set-a-default-share-for-all-scheduled-issues-in-a-project

Please vote for this feature.

Cheers,

Łukasz