twitter youtube facebook linkedin email
Connect with:

BIM 360 Release Notes

UPDATE: We have found some bugs related to this update and hence we reverted to the previous issue assignee permissions.
We will turn the update back on once the problems are resolved.


Issue assignee permissions update

Until now, when a user was assigned an issue, they could modify all of the fields in that issue. In response to customer feedback, we are changing the assignee permissions to provide more control over which users can change fields within an issue.


The new issue assignee permission structure

1) Users who have project issue permission settings less than “Full Control”
When that user is assigned an issue, they will be able to:

    • Add comments and responses
    • Add attachments
    • Change the issue status (except to closed, or move draft to open)

2) To perform the following actions, a user must either have “Full Control”, or be the issue owner (either as the creator of the issue, or designated as the owner following issue creation):

    • Re-assign the issue
    • Change the due date of the issue
    • Close the issue
    • Modify the text of the description
    • Modify custom attributes




Potential actions in line with this change:

  • If you do not need issue assignees to be able to modify all issue fields, then you don’t need to do anything.
  • If you have specific project members who need to be able to view and modify all project issues, those members should be granted “Full Control” permissions in issue settings in Project Administration.
  • If you need to allow specific project members to modify more fields in a specific issue, you can assign the project member as the owner of the issue to grant them the necessary editing permissions for that issue only.


MktoForms2.loadForm(“//”, “572-JSV-775”, 2332);

#mktoForm_2332 > div:nth-child(3) > div.mktoFieldDescriptor.mktoFormCol > div.mktoFieldWrap.mktoRequiredField > div.mktoGutter.mktoHasWidth{
#mktoForm_2332 > div.mktoButtonRow > span > button{
color: #fff;
background-color: #1858A8 !important;
background-image: none !important;
border: 0px !important;
#mktoForm_2332 > div:nth-child(3) > div.mktoFieldDescriptor.mktoFormCol > div.mktoFieldWrap.mktoRequiredField > div.mktoLogicalField.mktoCheckboxList.mktoHasWidth.mktoRequired, #mktoForm_2332, #mktoForm_2332 > div:nth-child(2) > div.mktoFieldDescriptor.mktoFormCol > div.mktoFieldWrap.mktoRequiredField
{width: 100%!important;}
#mktoForm_2332 > div:nth-child(2) > div.mktoFieldDescriptor.mktoFormCol > div.mktoOffset,#mktoForm_2332 > div:nth-child(3) > div.mktoFieldDescriptor.mktoFormCol > div.mktoFieldWrap.mktoRequiredField > div.mktoGutter.mktoHasWidth, #mktoForm_2332 > div:nth-child(2) > div.mktoFieldDescriptor.mktoFormCol > div.mktoFieldWrap.mktoRequiredField > div.mktoGutter.mktoHasWidth{
display: none;
width: 75%!important;
width: 84px!important;
#mktoForm_2332 > div:nth-child(2) > div.mktoFieldDescriptor.mktoFormCol{
margin-top: 10px;
width: 100%;

Subscribe to email digests.

Featured Links

Roy Goldschmidt


View by:
Most Recent Oldest
  1. AvatarTanyaEr

    We experienced opposite behavior – anyone (with VIEW+CREATE permissions) can change owner and be able to change the issue status (including to closed, or move draft to open) and change values in any attribute

  2. Avatarwendy.busschots63HMP

    We encouter problems with these ‘new settings’. An issue creator/owner (with VIEW+CREATE permissions) isn’t able to close the issues he created/owns. Is this normal behavour ?

    1. Avatarlucas.ferreiraH38JW

      It happened to me too. It was as if no permission worked. The suggestion that the support gave me was to withdraw permission from the function and add again. This, although very laborious to do, has worked for me.