Expand my Community achievements bar.

Lock updates in the issue once it has been converted into a Project

Avatar

Level 3

5/30/24

Description - Once an issue has been approved, we convert it into a project, and I would like to lock the comments (updates section) in my issues (nobody can enter a new comment) once it has a resolving project related to it. 

 

Why is this feature important to you - once the issue is approved, we follo up everything in the converted project but many time requestor does not know and he/she comment in the issue instead of the project this causes confusion in the Requestor because, he does not know that the latest updates are in the project or the executor do not see the comments because He is now working in the project. It results in lost the conversation chain and often gets missed. 

 

How would you like the feature to work - A feature where it detects the issue has a resolving project and lock any new comment.

 

Current behaviour - only technical method to achieve this is by revoking users' sharing permissions from the issues. Yet, this action would result in users being unable to view or access the issue unless they possess system administrator privileges. We still need Requestor has access to the issue, but he should not be able to modify or comment it. 

3 Comments

Avatar

Level 2

12/18/24

I have one user who constantly adds his updates to his initial request instead of the project. I would love for closing updates on the request to be an option!

Avatar

Level 3

12/18/24

Hi @SCainWabash 

 

I did an automation to create an issue comment once it has been approved with a direct hyperlink to the project comment section (see attached screenshot) while WF team accepts this idea. It´s not the best option but I have seen reduce the number of people who comment in the issue instead of the project significantly due to is easier for requestors click on the link instead of look for the resolving project.

 

I hope this idea works for you too.

 

esalraz_1-1734551618808.png