Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Is there a way to disable - not remove - a post function?

Montana Fox
August 13, 2020

I'll cut to the chase. I want to temporarily DISABLE a post-function, without having to completely delete it and then recreate it from scratch again later. Is there a way - either built into Jira, or with an add-on - to accomplish this?

I'm on Jira Core Server 7.2.7. Hoping to upgrade to 8.5.x this year.

3 answers

1 accepted

1 vote
Answer accepted
Rick Crow
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
May 25, 2016

@Martin Suntinger, I believe this is resolved. If I remember correctly, the two initiatives were assigned to two different releases. One, simply '2016' with appropriate, fixed start and end dates, the other '2017', also with appropriate, fixed start and end dates. What I discovered was the horizontal order of the releases in the Releases screen is at play with event ranking ... and, while the dates of my 2016 and 2017 releases were correct, the releases themselves were ranked 'backwards'. I.e., 2017 was to the left of 2016.

0 votes
Martin Suntinger
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 25, 2016

Hey @Rick Crow, is problem still open or has this already been resolved on another channel? This sounds very odd, could you try to re-index and re-balance The rank? (https://confluence.atlassian.com/display/JIRAKB/LexoRank+Management) maybe something got out of order there, otherwise we'll have to investigate this with a support case. Thanks! 

0 votes
Rick Crow
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
May 11, 2016

@Martin Suntinger: This is one of the behaviors that continues to cause me to hesitate pushing for broader adoption in our organization. I encountered this behavior in the earlier, non-live-plan version as well, so I don't believe this is specific to live plans. Thoughts?

Suggest an answer

Log in or Sign up to answer