Nic Brough -Adaptavist- Expert

Ok, so include that in the query clause that excludes issue types.

No risks, a new field will work fine for you. It'll be recorded in the change log, I'm wondering what you have seen that makes you think it might not?

I am fully aware of that, I've been working with Jira since version 1 was released. It does not explain what the problem is.

No, there's no way to edit the issue, you have to push it through a transition that clears the resolution, or find an app that can clear it (Sales alert - this was one of the very first things Adaptavist built into Scriptrunner as a "canned script" - a script embedded that you can just run, not have to write)

Again, the sub-tasks are not sprint items. In scrum, you commit to delivering a set of items, not bits of them. You estimate the items, not parts of them. And you deliver the items, not bits of them. All sprint items should have estimates that fit within the sprint. If you can not estimate an item low enough to fit, then…

Welcome to the Atlassian Community! No, the reason Scroll Versions exists is because of exactly this - Confluence doesn't support multiple active versions of the same page.

It's better to use the tiny link, in my opinion. If you move the page to another space, the standard URL will change to include the new space key, but the tiny URL will not change.

Welcome to the Atlassian Community! No, Confluence is a wiki publishing platform and when you want to export a page, it expects to simply export the whole lot. You will need apps to hide parts of the content from export.

Welcome to the Atlassian Community! Not for a while - Atlassian still have enough customers running servers on windows that it is worth it. But with most of them going to Cloud (The overwhelming majority of DC users use Linux clusters, I've helped move four people from Windows Server Atlassian to Linux DC installs over the…

Moving issues between projects, especially from JSM projects, is a bad practice and is not something you should be doing as part of a standard process. Automation, and the advanced clone apps you can find in the marketplace do not do it because moving issues needs checking that the data on the issue is valid for the new…

This sounds like you have an automation or script that is acting in your name. Start with a look at the automations you have set up in the project, and then the global lists of automations and listeners.

It usually means that the vendor has effectively stopped supporting it, they have been in one or more of the following states for a significant length of time: * They are no longer actively developing the app * They have no route to raise a support request * The documentation has gone away * It has failed Atlassian's basic…

So how are you identifying "non development issues"?

Confluence has some simple markup for inserting some emojis - (/) and (x) are the two you have in your screenshots. See https://support.atlassian.com/confluence-cloud/docs/use-symbols-emojis-and-special-characters/

The Automation rule looks fine, you will need to get your admins to get rid of the duplicated field - just rename it, no need to delete it.

Ok, great! All you need to do is change my "(subTaskIssueTypes(), Intake)" to "(subTaskIssueTypes(), "Project Request","Project Work")"

Welcome to the Atlassian Community! We can't tell you a lot about an error message you have not given to us. Please could you explain more?

I was guessing that you had an issue type called "intake" from "with the exception of sub-tasks and intakes". How are you actually identifying "intakes" if it is not by issue type?

Sub-task time estimates do roll up into issues, when you view an issue the estimate section has a tick-box to toggle "include subtasks" in the time panel, and the issue navigator lets you display a set of Σ fields that add up all the values in a sub-task on to the issue of which they are a part (Σoriginal estimate, for…

You have to descend into each of the screens in order to add fields to them. Sprint is not on display by default, because a Scrum board, by its very nature, displays things in the current sprint, and groups by it in the backlog (that's what a backlog is for!). Kanban boards do not show it because sprints are a Scrum…

I want to be very clear about relationships. I work for an Atlassian partner, Confluence is where I and the rest of our people go first, and it usually works. We are not ready. But. * Tables * Sorting * Headers * Being able to embed proper metadata * Search * and * and * and There is some Adaptavist stuff I could talk…

Yes, someone else has already created a status with the name you want to use. Whilst Jira allows us to create fields with the same name (it did not use to and I really want to go back to that behaviour), it has never let us duplicate status names. You will need to talk to the admins about the status you want to add.

Welcome to the Atlassian Community! You do not. Most Atlassian systems assume that a user can use everything you have installed into it (because the way the licences work means you have to buy apps for all your users). There are a few exceptions - some apps do have permissions internally, but how they work is up to the…

Welcome to the Atlassian Community! I am slightly confused by this question. When I use the meeting notes template to create a page, I get a page. Not many pages, just one new one each time I want to write up a meeting. What are you seeing it do that is different from that? Or what do you want it to do that is different?…

Great! Column-to-column moves have some complexities in the underlying processes. A board is not a container of issues, it is a view of a pile of issues. Each column is a grouping of status into a single column. In most cases, there's only one status in each column, but it's not unusual to see columns with more than one…

Ok, that has helped me understand, but I am not sure I have this completely right. This query will find issues linked to your Epic (meaning with issue links) issue in linkedIssues(ABC) AND Status not in (closed, de-scoped) AND issuetype not in (subTaskIssueTypes(), Intake) This query will find issues in your Epic (meaning…

You are right, there is no "account merge" on Cloud or Server/DC.

Automation does not have functions for moving issues - issue moves should not be part of a standard process, they are for housekeeping, migration and genuine "oops, created in completely the wrong space" mistakes.

No problem, it's the main reason people ask questions! There are two ways to do that. There is the "copy workflow and add new status" option as above, and you could rename "Opened" to "Open", assuming you do not already have a status named "Open". I would recommend the rename, "Open" is a better word than "Opened" for a…

Welcome to the Atlassian Community! Where are you trying to do this? Have you gone to Admin -> Issues -> Issue types and clicked the "add new issue type" button, or are we looking elsewhere?