Nic Brough -Adaptavist- Expert

Not on Cloud, the title of a page is an integral part of the view.

It's not "wrong", the last column is how Scrum and Kanban define it. For company-managed (classic) software projects on Cloud (And all Software projects on Server), the boards can work fine with you on this - you map the "cancelled" status into the "done" column. For team-managed projects, and business projects, no,…

Ok, yes, you could use Scriptrunner to do this, but before you go down this route, I want to question why you're doing this. What you are describing here is a form of ranking. There are two questions that jump out when I realised that it was ranking: * Why are you not using the ranking built into Jira Software or the…

I'm afraid that really does need to go to Atlassian support, we can't tell you what it is (We're a community of people who talk about Atlassian, we have no access to the back end of Cloud systems)

The most simple way to do this is: Backup your current server (database and attachments), build a new service on the target server, restore the backup into that. Now you have two separate systems, so choose which one is going to be which and, * on the Software service, delete all the service desk projects, then remove the…

Yes, you must make sure that your stories and all of their sub-tasks are all in the last column on the board (it is usually called "done", but it doesn't have to be named that). That also means that the issues have to be shown on the board (the filter needs to select for them) If you don't want to see the sub-tasks on the…

I am sorry, but that explains nothing about why you've given us a page tree or what the problem is.

They are admin objects, you create them under Admin -> Issues -> workflows. Most of us do not do that though, we create (classic or company managed) projects, which generate a workflow to get you started with, and then dive into editing that.

Jira Software's hierarchy is Epic -> Issue -> Sub-task. Atlassian themselves have said Epic is mis-named, it should be Feature, but changing its name is not trivial (and breaks some apps if you only rename the issue type). Exactly as you've found, Advanced Roadmaps create layers above Epic, not between it and Issue.…

No, there's no blanket permission like that, in either team or company managed projects, you have to amend the permissions for each on (although with company managed projects, you can share permission schemes)

"Account suspended" message tells you why - "Your subscription for Atlassian Cloud hasn't been renewed." You'll need to bother your site administrators, find out when they're going to pay for the service and get it re-enabled.

Yeah, there are things like this that have been there for years, even since before it was forked from Server (Server also has exactly this problem)

Ok 1. For team-managed projects, the owners can add fields from the project settings. For company-managed, a Jira admin has to set up a new field and attach it to the projects. 2. Do you mean on a board (use quick filters) or in general? (Go to issues -> search) 3. Blank out the epic link on the issue 4. It doesn't stop…

Confluence uses a different system, I'm not sure where to change those. As for the html, yes, that should work.

This script does it for issue type restrictions based on role, but the same principles apply to most drop-downs - https://library.adaptavist.com/entity/restrict-issue-types

Ah, sorry, I missed that step out. Jira does have an "any logged in user", but Confluence is a little more simple and usually just has a place for "group(s) that can log in to me". On Cloud, that's defined in the application access for your site. Almost all Confluence systems I've seen keep this simple - there's a single…

The default is to drop logging data into the application log, but that can be changed if you're willing to mess with log4j settings, or a particular app supports separate logging. Also, you may find that an app only logs errors. From memory, JSU logs global config change and errors, but not actions that are part of…

No, the fix version is 8.17, so lower versions will generally not contain the fix (or may not even have the problem) The exception is the long-term-releases (8.5 and 8.13) - their point releases may get retro-fixes to enable people to stay on them for longer.

No, the email handlers are quite simple, and don't do much more than "create or comment". They take their summary from the subject and the description from the body of the email. Some can be configured to try to strip conversational replies out. They'll look at the sender and set that as the reporter, and if you're using…

Just to be clear (as my colleague has just misread this!) - Other people using your filter will see the changes you make, but it's not an "automatic update" - you're only changing one single object. If people have made their own copies of your filter, they won't be affected either, their filters are separate objects.

Oh, yes, I see. That won't happen - Epics are not sprintable items really, they're overarching containers (that Jira represents as issues, so you can use a lot of standard reporting and searches on them), but as they don't have their own estimates and their process is not really handled by a team, it's more "it's done when…

You keep ownership of it, but other people can run it and get the results from it. If you change the filter, then yes, you're changing what everyone gets (there's a single search behind the filter, not one for each user). Other people can change it once they've run it, but they cannot save those changes to your filter,…

Does the app support per project config? That doesn't matter to the licencing though, your licence must match that of the server you have installed it on. A 20 user licence for an app will not work if you have a 100 user Jira server, you need a 100 user licence for the app.

Deleted issues are gone, there's no way to report on something that isn't there. You can take a guess by looking at the holes in project numbers - for example if you see ABC-123, ABC-124, ABC-126 in a project, then ABC-125 has either been deleted or moved. You should be able to check for moved by searching for it, Jira…

That is not how apps work. They are installed on the Jira Platform, and made available where ever their definition says they should appear. If you want to limit an app by project, then the app has to implement the ability to be configured on or off for a project. Most do not do this, but some do, and when they do, you…

I think that's the right place to do it. A .vm file can be thought of as "processed html". Imagine the system processes it a line at a time. As it reads each line, it simply copies them to the output, unless it finds a directive or variable. If your desired text is just simple fixed html, you can put that straight into the…

You can't change the administration of the projects. It's not even a case of changing the way admin works - the things Team-managed do that Company-managed do not, and vice-versa, simply don't exist, they're not just locked down. However, most of your list is already possible, without having anything to do with admin…

Interesting problem, could you try a bit of a test for us? Create a new page, doing these little things: * Enter a title like "test toc page" * Type: some text as the first line * Type: /h1. heading 1 * Type: /h3. heading 3 * Type: /toc * Type: some more text to end the page test Save the page and tell us what you see on…

For a Service-management project, you probably want to look at the "email channel" for it - https://support.atlassian.com/jira-service-management-cloud/docs/receive-requests-from-an-email-address/ - but, that might not be right for you if you are also gathering human generated requests from email. For non…

Ok, you're going to need something like scriptrunner to read the history and calculate the field for display in the dashboard