Nic Brough -Adaptavist- Expert

We can't start to look at a problem we can not see. The screenshots are fine, we can see them, but you still have not told us what you are doing that gets the problem. Could you please, please, please, describe what you are doing that gets the problem to happen? As I've asked for before, just a simple walkthrough of the…

Yes, we know that it is happening all day. What we need to understand is what you are doing that triggers it. Could you please describe what you are clicking on that causes this behaviour?

But when is it happening? Can you tell us what you are doing that then leads to the refreshing?

I am sorry, I am obviously not being clear enough in my question. Can you tell us exactly what you are doing that causes this? What exactly are you clicking on to cause the "refresh" to occur?

But what are you doing that causes the refresh?

No, issue links should be irrelevant. The only things that matter to sprint completion and carry-over are open sub-tasks and being in the last column of the board. I think we need to see the details now - an issue that was carried over when it should not have been, with it's history, the board config (column configuration…

Technically, you should use your developer licence for "cold standby", but the reality is that the best cold-standby setups are replicating the production database, so they contain the production licence. The developer licence is used to get the cold standby server set up and tested. Depending on the exact nature of your…

It is a little complex, but so is what people are trying to do here with Epics (and there's a long history of how they've been implemented in Jira, and ended up in what I can best describe as a "clunky" state)

To create a common backlog, your teams will have to work on one board. It's not immediately obvious from the docs and tutorials, but a backlog is not an independent thing - it is part of a board. The backlog is best thought of as a "feed" for a board - it's the issues that are candidates to end up on your board. If you…

The immutable tiny link is a url for the page within the application. Sharing a page means you are creating a (possibly temporary) place for a page to be seen without someone having access to the application (including any other pages that might exist) Browsing a Confluence system, and getting a shared page from someone…

Cloud apps do not allow you to get into the core code in Jira - there's no way to mess with the layout of backlogs. The best you could do is adding a formatted field app, but I'm not even sure the backlog would display anything like that.

Confluence does not have a "page owner". The person who created the page is the creator or "author", not the owner, and you should never change that because it destroys the information about who initially created the page, which in a lot of cases, is potentially illegal. The "owner" of a page at the moment is effectively…

Um, no. They're different things. The tiny link for a page is a unique and immutable link for the latest version of the Confluence page within the installation. The shortened link for sharing a page is for sharing a page, it can be changed and it can go away.

Welcome to the Atlassian Community! It's either a bulk import, or you'll need to write something that can read your data from Yuque, and convert it into REST calls to create pages in Confluence.

What exactly are you clicking on?

Welcome to the Atlassian Community! Just to set some expectations here - unless this gets a tidal-wave of votes, or suddenly starts to fit in with Atlassian's longer-term plans, 8 years is not unusual. My favourite example, which I've sadly no bookmark for, was a request for (amongst other things) "priority schemes".…

For a bit of background, yes, a lot of us have been complaining about this for a long, long time. Most of the ecosystem has seen the dual summary / epic-name as, at best, a tiresome waste of effort, and at worst, utter nonsense. From the beginning, most of us simply wanted the summary to work as the epic-name. It was not…

What happened when you tried a couple of letters? Ideally (just for this test, not generally), could you pick a group name that you would expect to have lots of other groups that start with the same few letters. Or even just try "s" in the search, and show us what the screen looks like now. We'd need to see most of what…

Welcome to the Atlassian Community! As I pointed out earlier, the worst possible thing you can do for reporting on Jira is read the database. You should stop doing that., for exactly the reasons you are seeing here. But, how exactly are your tools that are reading the database extracting the data? Are you entirely sure…

There's no built-in function for this because that is absolutely not what Story points are for. In Scrum, they are used to estimate and report on the team. Not micromanage individuals. Also, you can't do it - one person's 5SP story is another team member's 3SP story.

Could you show us the configuration of the post-function please? (Click on the edit pencil). Are you sure the workflow has been published and is active when you're creating new issues.

All your data in the app will stop being usable, and your CLI integrations will stop working for all existing issues.

The edit and transition screens only show the fields the user is supposed to be able to edit. I don't think anyone needs to see the whole issue they've just read and decided to edit/transition in front of them on the update screen, they only made that decision a few seconds ago and can probably remember why they're…

Welcome to the Atlassian Community! What import are you actually running here? And what does your data look like?

Welcome to the Atlassian Community! Could you describe what you mean by "reloading itself"? I know roughly how the web works. When I click on a link like "create issue", "show me an issue" or "transition an issue", it takes me to the view of the issue I've just created or amended, I expect that. But there's no "reload". I…

Oh, there is a lot to this question, when I opened it up, part of me wanted to write a long essay on it. I will try not to. You have a Jira server licence. (Confluence is the same model, so I don't need to repeat for that) Technically, the rule is 1 licence = 1 server. If you are on 25+ you have a "developer" licence that…

Welcome to the Atlassian Community! Jira has a lot of ways of trying to contact people, and only your admins can really explain what they have set up. I'm sorry, but we can't help you. You need to talk to your Jira admins.

Ah, yes, makes sense, but there's a better approach than a JQL field. (Not a bad choice though - a JQL-based field is probably what is stopping you from posting "my Jira takes 25 minutes to render issues" problem!) The last time I ran into this, we rigged up the build systems to create Jira versions in the project(s)…

Fields are locked to prevent people from misconfiguring them. But it's a broad sweep - a lock on a field might only be there to stop one or two mistakes (like Epic Name being optional on Epics or added to non-Epic-level issues), but it then locks down all the other things that might not actually be a problem to change.…