How to keep ticket order while moving a ticket across columns

[tomicakorac]

In older Jira Server versions, when I move a ticket from one column to another in a Scrum Board (let's say from 'In progress' to 'Done'), the ticket's order was preserved compared to all other tickets in the board. I could only select the column to which I want to move the ticket, and not re-order the ticket in comparison to other tickets that already exist in the new board.

In the Nextgen project board, while moving a ticket across the columns, its order gets lost. Along with choosing the new column for the ticket, I am also forced to also choose the tickets order compared to the other tickets existing in this new column.

Can I (and if yes, how) revert my board behaviour as it was before?

[Jobin Kuruvilla [Adaptavist] · Accepted solution]

What happens when you do the same search in Confluence itself? Does reindexing in Confluence fix this?

[Jobin Kuruvilla [Adaptavist]]

What happens when you search? And are there any permission differences?

[Rumceisz]

Hi Jobin,

when I directly insert the URL to the browser, it navigates to the proper page in Confluence.

[Rumceisz]

I am Jira administrator and have access to all spaces and it doesn't work for me too.

[Timothy Nash]

Been struggling with this too. It was intermittent for me and I discovered that some special characters in the document names were causing this. I had parenthesis and removed them and viola, it started to link without errors.

[Tshepo Mogorosi]

Before running around checking all sorts of things and editing xml files, please check the base urls for both applications, had the same problem and that is how I resolved it.

[alexbethke]

I run Jira and Confluence on two different Domain Names. When I insert a Jira Ticket into a Confluence Page, Jira tries to show the Page in the 'mentioned in' area. Unfortunately an error occurs everytime the Confluence Page is loaded. This is the message in the console: Failed to load resource: the server responded with a status of 500 (Internal Server Error) http://servername//rest/viewIssue/1/remoteIssueLink/render/10001

[Chris McFadden]

I had this problem and was able to resolve it by allowing Anonymous read-only access to Confluence. Part of the problem is that our user directories are different in JIRA and Confluence at this time, which we plan to fix soon. In the meantime this works fine since our wiki is not publically accessible anyway.

[Theodore Tzidamis]

Hey Rumi,

In your logs you might be getting something like

Failed to load Confluence Page from remote server Caused by: java.io.IOException: Failed to load Confluence Page from remote server Caused by: com.atlassian.sal.api.net.ResponseException: Status Code: 200, Status Text: OK, Errors: {}, Error Messages: [java.lang.Exception: com.atlassian.confluence.rpc.RemoteException: You're not allowed to view that page, or it does not exist.]

Can you please check if that is the case?

[Chris McFadden]

I am having the same problem. On Confluence 4.3.2 and JIRA 5.1.7.

The odd thing about our config is that both are on the same server and Confluence and JIRA have different user directories.