Nic Brough -Adaptavist- Expert

Welcome to the Atlassian Community! You can not enable this in Confluence Cloud. My understanding is that a chunk of the code for it has been deprecated and actually removed so that it wouldn't work anyway, but they've not got around to cleaning up the UI yet.

Welcome to the Atlassian Community! This is what it says it is - the certificates are not right. Jira does not do any SSL certification or validation itself, it's done by Tomcat or the proxy or load-balancer in front of Jira (I rarely set it up in Tomcat, it's far easier in proxies) You'll need to start investigations at…

Welcome to the Atlassian Community! What user directory are you using for your Cloud system? Is it Atlassian accounts, Google accounts, or Atlassian Access? Jira can only ever send email to the address associated with the account that the user is using, but you can play tricks with a couple of those options.

Yes, I watched it, there's nothing in there that isn't a 401 authentication problem. Could you explain more about why you think it is not an auth error?

Welcome to the Atlassian Community! For Cloud, you would need to use Atlassian Access to be your user directory, and hook that up to import your users and groups from Microsoft 365 (or make it use the same directory MS-365 is using)

The best option is to use Created vs Resolved. This does mean that you have to use the Resolution field as Jira intends it to be used, but that does offer you a lot more flexibility and power than just "closed", and it will make all the other reporting in Jira work properly as well.

Welcome to the Atlassian Community! The only text "correction" Atlassian have in their software is to correct the capitalisation of their trademarked "Jira" (it used to be called JIRA, people still type that). Whatever is happening here, it is being done by the user's browser (or extensions for it - I use a couple that…

Ah, a challenge :-) Imports are not a problem - you'd get "can't find out how to do this" type errors. Like "please multiply 6 by blue", the message would be "blue is not something any of our libraries know how to multiply by 6". If your imports were wrong, you'd get "unrecognisable function" type messages. NPEs are what…

Welcome to the Atlassian Community! Jira, with Jira Service Management added to it, is not as simple as it could be. (Long, history, you don't need to know it to understand what I'm about to type) Jira provides projects which contain issues. Your people (JSM agents) will be working mostly with issues. JSM adds a layer for…

That's a good idea, and it's worth looking at! It will be down to your processes though. Generally an "Approver" is someone who would look at a new piece of work that is arriving through a Service Desk, It's a bit earlier in the process - Jira tends to assume an approver will be looking at change requesta, a request for a…

Welcome to the Atlassian Community! There is not enough information in your question to begin to answer it. What do you mean by "products"? Atlassian products (applications and apps)? Vendor products in the marketplace? Products as a custom field in one of your Atlassian systems?

Welcome to the Atlassian Community! Jira has no "keep deleted issue" function, other than the project trash, which keeps whole projects and all their issues. (It's actually just a flag that completely hides the entire project) The apps I've seen provide "restore deleted issue" are relying on one of two things: * You have a…

I'm very fond of quick-filters like "issuetype not in subtaskissuetypes()". It means no-one has to mess around with the filter when people change the issue type list for their project.

I can't see anything in there that is not a 401 authentication problem. (It's not "commonly associated with", 401 is defined as an authentication problem, and should never be the return code for any other problem. Although authentication problems could be wide and varied) Could you explain more about why you think it is…

Welcome to the Atlassian Community! Jira does not record the date filters are created. If you looked in the database or REST calls, you'd get a numeric id, which always increases, so you know that filter-123 was created before filter-456, but that's it.

Welcome to the Atlassian Community! The easiest way to get this to happen is re-configure your board. I suspect you will find that you have removed the status that those issues are in from the "done" column (the last column on the board). Have a look at their status and the column mappings you have for them!

I keep forgetting that trial licences don't care about number of users or whether it's DC or Server!

Welcome to the Atlassian Community! You don't enable a base level issue type to have sub-tasks, you tell a project that it has one or more sub-task types, which then enables all the base level issues in the project to have sub-tasks Epics are different, they currently represent their child issues by a link.

Welcome to the Atlassian Community! Macros are only one thing apps can add to There's no way to know what an app is doing for a user unless the vendor has built some form of logging into it. Apart from macros, you're going to need to look at each app, work out if and how it might be recording activity (if at all) and read…

Welcome to the Atlassian Community! No, there's no way to do this. A Kanban board is a representation of a process flow, so the only thing it could do here would be to have a process where you had your five priorities as status. Which wouldn't really be a process. But, if you're willing to look at apps, there are some…

The views of an issue are consistent, and they will look the same across all the users. But there are a number of different ways of looking at issues, and my best guess is that you are tending to use a different one to the others. To further debug it, I'd want to compare the exact differences you get, after checking that…

Welcome to the Atlassian Community! Yes, that's correct, the assignee field is the person responsible for getting it done. Your reviewer field is just someone associated with it as a reviewer. I would probably take a look at copying the reviewer into the assignee field when the issue reaches the review stage.

By Ecra, do you really mean Jira?

We've had some tries with it at Adaptavist, and in the Community, and the answer is currently a resounding "no". Adaptavist fed it 250-ish questions on Jira and Confluence, ranging from simple "how do I" to quite over-clarified questions. We had a Community lead hook it up to Community and we deleted all 150 answers and…

Welcome to the Atlassian Community! The level of licence you have applies to the workspace, not people. If you're working on the same project, in the same workspace, your people are all consuming either free, standard or premium licences for it.

So, that means Jira can't know who the reporter is. There's no way it can email people it doesn't know about.

Yep, most people do that, but with a one-liner explaining why they did it (unless it's really easy to understand)

Welcome to the Atlassian Community! The best practice is "don't". Jira does not have group assignee functions because it's a bad practice - the assignee should be the single person currently responsible for getting an issue done. There is no harm, of course, in having a field for "the group that you talk to if the assignee…

I've just noticed - the issue you are showing us that has "Epic Name" on it does not have "Epic Status" beneath it. I'm not sure it is a true Epic type. You could have an issue type called "Epic" that is not actually an Epic, and have added a field called "Epic Name" to it.

Yes, if you set up the notification scheme for the project to send email to "reporter" on issue create. People can opt out of "email me about changes I make" though.