Nic Brough -Adaptavist- Expert

Why not? A lot of people find it quite useful. Those that do not simply ignore it. If you're worried about it exposing information you don't want to share, then look at the permissions for the pages you want it to not report on, the activity feed only shows data to people who have permission to see it.

Er, no, it's doing what it's supposed to. If you've chosen to put proprietary information in your Confluence and not secured it, the activity feed is just one way you are exposing it. There are plenty of other ways that you have chosen to let people see it. You need to take a look at the permissions you've got on the pages…

I'm afraid you'll need to find out which of the other administrators removed your access and get them to put it back.

No, you'll need an app to provide that higher layer. Advanced Roadmaps (which used to be called "Portfolio") is the Atlassian way to do it (for which you need to go up to Premium)

That's exactly what the field context is for, for most custom fields. Labels are different, please see my answer

There no profiles "installed by related add ons", I do not understand what you are talking about.

Smartsheet does not have an export function that can do this, you'll need to build the workflows and fields in Jira by hand, then use a CSV import to bring the issues into the new projects.

You don't, at least not by "moving to another board". Boards are not containers for issues, they are a view of a selection. I can't think of a good reason for cloning an epic and sticking it on another board, it sounds like you have a clunky or broken process, but if you insist on doing it, then yes, you can do it. It's…

No, only the issue navigator has an export to excel.

The two stories are not sub-tasks, they are stories in their own right, with a dependency on each other. You say they need to be done by different teams, and that's one of the ways to define something as a separate story.

Hmm, that's odd, the only way I can do that is to have an administrator turn off the table module, which turns off a load of other functions as well. Have a word with your admins about getting it turned back on.

You will need to raise this with your administrators, they can investigate, and then raise a support request with Atlassian or the vendors of the app.

You can't do that with custom fields, but you can with issue security. This lets you set a "level" on an issue that limits visibility further than the project's "browse" permission, you can set up levels to allow totally different sets of people to see issues.

Yes, you can use "bulk edit" whenever you need to. But I'm a bit stuck on why you'd want to do this. Your listener is posting data into a database, but why do you want to do this on view? The issues have not changed, so your database is not going to get new data.

You can't do this, Jira software only does Epic -> Story -> Sub-task. If you want layers above Epic, you will need to go up to premium to get Advanced Roadmaps, or buy one of the apps that provided more layers (Big Picture, Structure etc)

They are not supposed to add up to the stories estimate, they are independent of it. Use the Σ (sigma) fields to see the sum of estimates from an issue's sub-tasks.

That has to be a case for looking for a "search and replace" function, not a template or theme thing. Or, better, you should have had your people create pages that use a single included page rather than copying common data.

This is what it says it is, your database is not configured correctly, and you need to correct the collation settings on it before Jira can use it.

The issue here is with your processes and data structure, not the software. You need to stop trying to use sub-tasks as work items in their own right, they are not issues themselves, they are parts of an issue.

There is no way to do this, components are distinct across projects, you can't pretend that two of them are the same thing just because they have the same name. I don't know if you're using the components for other functions, but if you are not, your best option might be to create a multi-select custom field for all the…

No, you have to create a new project, then move all your issues into it.

Just add epics to the list of possible issue types for the project

Because not everyone uses boards. And when you do, sometimes you do want a status to be green when it is not in the last column. And yes, the workflow editor lets you set them, but not in the workflow, it is a property of the status, not the workflow.

They appear automatically.

Actually, no, it is not useful because your team does not need to see issues they have finished

You will need to talk to your administrator, probably the one who removed your access. If you can't find them, then you will need to raise a support request over at https://support.atlassian.com/contact

I am sorry, but the first part of your question does not make sense: >Would like to aggregate status as SQL allows into a defined name and Aggregate where? Aggregated status is nonsense because it tells you precisely nothing about what is happening. The only aggregation that makes any sense is to automate the Epic status,…

I don't think this is a simple field you can generate with code within SR, you're asking to select one thing while displaying another. I think you'll need to write an app to do this.

What scripting or automation apps do you have? (You'll need one to do this)

Which utilisation report are you looking for?