Can we disable linking issues to an Issue when it is closed

[Vishnukumar Vasudevan]

Hi All

Is there a way to restrict linking issues to a closed issue ?

Thanks, Vishnu

[Jobin Kuruvilla [Adaptavist] · Accepted solution]

Can you try removing the permission using worklofw properties?

http://www.j-tricks.com/1/post/2011/02/permissions-based-on-workflow-status.html

Haven't tried that for linking but it surely works for some other permissions. Worth a shot.

[Vishnukumar Vasudevan]

Jobin

Thanks for the link. It's similar to http://confluence.atlassian.com/display/JIRA044/Workflow+Properties

But I don't see any properties for restricting Issue Links.

[Jobin Kuruvilla [Adaptavist]]

You don't restrict the property. You restrict the permission as mentioned in the above post. Something like:

jira.permission.link=denied

If that doesn't work, try:

jira.permission.link.group.1=some-group-one

where some-group-one is a group that aready had linking permission but doesn't have any users in it or has only limited users like admins.

As I said before, I haven't tried this purticular example but it should work.

[Vishnukumar Vasudevan]

Thank you so much Jobin.

The second one works well.

[Stephen Chai]

Hi, I tried to disable linking but it only works when I want to disable Issue A (closed issue) from linking to issue B. It doesn't prevent me from linking Issue B to Issue A. My aim is to prevent any blocking issue to Issue A as long as it is closed, as this breaks the workflow I have set up. Any help will be greatly appreciated. I'm new to Atlassian and am now trying to learn how to configure it for our workflows.

[Ilya Turov]

kinda late to the party, but just adding 

jira.permission.link.denied with empty value

to status properties seems to work

[Olaf Troike]

I add the property to the closed status, but it doesn't work. It only works when I want to disable Issue A (closed issue) from linking to issue B. It doesn't prevent me from linking Issue B to Issue A

[Сергей]

Dear Olaf, 

Did you found the resolution for this request?

[Jonathan Smith]

@Olaf TroikeI have the exact same question as you - did you ever figure out how to lock linking issue B to issue A?

[jira-admin_telenor]

@Olaf Troike @Jonathan Smith dod you guys find out how to restrict issue B from adding a link to issue A where the  jira.permission.link.denied is in place for issue A

[Jonathan Smith]

I have not found a solution.

[André Stuhrmann]

I did not know which one would be the correct property, so I have tried

jira.permission.link=denied
jira.permission.link with denied in the right column
jira.permission.link.denied - as suggested by @Ilya Turov 

None those would work. Any help?

André

[Tomas Slavkovsky]

This works:

jira.permission.link.denied

The answer is here.

[Nic Brough -Adaptavist-]

No, there's no way to do this.

If you wanted, you could investigate amending the core linking code to add such a check, but that's a lot of work (and I'm not sure the requirement is actually that useful - how do you link to duplicates or refer back to useful tickets?)

[Vishnukumar Vasudevan]

My requirement is, just wanted to make sure that No one links any CR's to a Release which is already closed.

[Katarina Nikolic]

Dear Vishnukumar, 

Did you found the resolution for this request?

Thank you.

Regards,

Katarina