Project

General

Profile

Actions

Defect #37685

closed

Read-only field permission for the project field is ignored if the current project has subprojects

Added by salman mp 6 months ago. Updated 5 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Issues workflow
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed
Affected version:

Description

When project_id marked as readonly in workflow/permissions for a role say role1, if a user with role1 try to create an issue in a leaf project, everything is ok. But if that user try to create new issue in a project that has some subprojects, that projects was shown in issue creating form.


Files

Actions #1

Updated by Mischa The Evil 6 months ago

Can you add some test coverage for this change? For it, you can check out these relevant references:

Thanks in advance.

Actions #2

Updated by salman mp 6 months ago

I have no experience in writing tests, but I hope these two tests can show that cases.

Actions #3

Updated by salman mp 6 months ago

second test function's name was wrong and this file fixed that.

Actions #4

Updated by Go MAEDA 6 months ago

  • Category set to Issues workflow
  • Status changed from New to Confirmed
Actions #5

Updated by Go MAEDA 6 months ago

  • Target version set to 4.2.8

Setting the target version to 4.2.8.

Actions #6

Updated by Go MAEDA 6 months ago

  • Target version changed from 4.2.8 to 4.2.9
Actions #7

Updated by Go MAEDA 5 months ago

  • Subject changed from Show project field in Issue create form when project_id is not permitted field to Read-only field permission for the project field is ignored if the current project has subprojects
  • Status changed from Confirmed to Resolved
  • Assignee set to Go MAEDA
  • Resolution set to Fixed

Committed the fix. Thank you for your contribution.

Actions #8

Updated by Go MAEDA 5 months ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF