Nic Brough -Adaptavist- Expert

Nope, the only thing Jira looks at when you close a sprint is which column an issue (and all its subtasks) are in. If the status looks to be correct on both issues and their subtasks (and please check that by looking at the issue view, not a search, report, or board), then the only explanation is that you've got something…

Yep, there's no such thing as "sub boards". Sprints belong to a board, but can be worked on in other boards.

Welcome to the Atlassian Community! You could script or automate something that generated some unique id, but it would not be of any real use to you as it wouldn't do much. It would be less functional than the issue key. Why do you think you might need this? What problem would a non-sequential arbitrary key solve?

Welcome to the Atlassian Community! Server (not DC) licences are "perpetual". Your server will continue to work fine for as long as you want. The only difference you'll see is the admins will get warning that you're out of support. After November 2023, you will have no support, and you will not be able to upgrade to a…

Welcome to the Atlassian Community! The general rule here is "use groups to define what we instinctively understand as groups of people, using them for product access and reporting, but NOT project access" and "use roles to define who can do what in a project" In your case, I would do this as a minimum: * Group:…

Mmm. So you want the workflow view to be inaccurate, according to the current state of the issue and the user meeting the conditions or not? Ditto, the board view - the whole point of a board is that it shows a common view of all the issues the team is working on. If you were to hide columns into which the current user…

Welcome to the Atlassian Community! * The best way to do it is ask the person who gave you the key - they should not have given it to you, as keys should not be shared across accounts. * If it was you who used the key elsewhere, then it's going to be about remembering where you did it. But either way, start…

Welcome to the Atlassian Community! There's a three layer hierarchy here, and it's important to be clear about where things are in it. * Epic is the top level * Base level issues are the day-to-day work items * Sub-tasks are fragments of their parent issues There is a quirk in here in that Epics can have sub-tasks as well…

Welcome to the Atlassian Community! This is only possible for Company-managed projects. Team-managed projects only support a single sub-task type (called sub-task. There are open requests to allow for more) For CMPs, log in as an admin and go to admin -> Issue types, add the ones you need, then go to the projects that need…

Welcome to the Atlassian Community! That's what the "shared" in "share a workflow" means - there's one workflow and many projects use it. So if you change it, all projects using it will be affected. The workflow schemes are the same - they are shared, so changing one of them changes all the projects that use it.…

Welcome to the Atlassian Community! You don't need to do this in this way. I suspect you're probably using URLs for these links, inserting something like https://your.org/confluence/pages/viewpage.action?spaceKey=SPACE&title=pagename You have a couple of options with this - * Use the page's tiny-link URLs - these don't…

Welcome to the Atlassian Community! There is no "prefix" in Confluence, you are inserting something into the title. So there's no way the pagetree macro can hide them, it can only show you what you have put in. The only way to fix this is to come up with a better naming scheme, one that's built around having unique page…

The stuff you've found about macros is correct, you can create user macros that can do this. But Cloud does not support user macros.

Jira uses that warning a bit more than it ought to (it applies it to templated projects as well as simplified workflow projects nowadays) The place you need to think about this really is just "simplified" workflows. These apply only to "company managed projects", where one or more projects appear on a board, and the (JIra,…

I won't repeat what the others have said, but I do want to ask why you think you want this version number. It is of absolutely no use to a subscriber to the service. The only use for it is for a bit of Compliance logging and the answer to "what version was/is it?" is "latest at the time".

Welcome to the Atlassian Community! You have not told us how this relates to your Epic -> Issue -> Sub-task hierarchy.

What app are you using to do this comparison? (Which app? As Jira doesn't have native comparisons like this)

Welcome to the Atlassian Community! I am not understanding why you are making this so complex. If you do not need a transition any more, remove it from the workflow. The board is reflecting your status, nothing else. It's supposed to show valid status. If you think a status is invalid, remove it from the workflow as well.

First hit on search engines is https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-issue-worklogs/ but I'd recommend look at the v3 API too.

>>We seldomly listen to people. We just hear them Yes, that, yes. Hearing people is one thing, but listening is deeper. Both of those words are about just talking, and that's not really right here - there are other ways people want to be listened to, and the route you get the communication from should not matter. For a…

Welcome to the Atlassian Community! Could you explain what this has to do with Atlassian stuff?

p.s. if you want to scare an older Atlassian admin, ask them about Themebuilder for Confluence.

So I will be clear that I have some bias here, as I work for Adaptavist. The content formatting macros is the first thing I reach for on every Confluence install, even before people come to me with an actual problem or improvement. But I've been saying something like that since I first got asked to be the "Atlassian…

It might be that the resources you were reading were talking about server instead of cloud. They are two different systems (Confluence Cloud's code base forked from server about a decade ago)

No, it does not. If you click "required", the link changes name to "optional" (which shows you that the field is currently required). I don't think this is the best way to show this, I would prefer an explicit and clear "this field is currently optional/required" display of some sort. But the toggle to other option is…

Welcome to the Atlassian Community! Please, do not SHOUT AT US. It is hard to read, and some people find it quite rude. Jira has several integrations with voice software and a remote API you can build on, but nothing built-in. You should start with a look through https://marketplace.atlassian.com to see what other people…

There is a feature request to get the "teams" field to work as a regular select list in searches and gadgets.

@Mayur Jadhav - it is just a point of history and description - "aligned with" is a great way to describe it, far better than I did. On the historical side, I think it's probably fair to say that Agile and Lean were partly inspired by the Scrum and Kanban methodologies.

Welcome to the Atlassian Community! If you are doing Scrum, I would recommend not doing this for issues that have been added into the current sprint, because it will distort your reporting. For things cancelled before the sprint they are in starts, or things in the backlog, it's fine to 0 the estimate. I would set up an…

I'm not sure "dragging your sorry ass out of a river" counts as "swimming", as I only had to swim a few yards to find a bit that wasn't too slippery to start wading on. I have fallen (or been pushed or thrown) into the Kennet River that runs through the centre of Reading more than once, and one of those falls was during a…