Nic Brough -Adaptavist- Expert

I can't tell you who your admins are, I'm just a community member here to talk about Atlassian stuff. I have no knowledge of, or access to, your system. My best guess on questions 1 and 2 is that your project admin role had "extended permissions" on your old service, but Cloud does not have that option, so you've lost it.…

As the products diverged years ago, any answer to that question is going to be a massive essay, which will just be a rewrite of the atlassian docs. Start at https://www.atlassian.com/migration/cloud/explore and maybe https://support.atlassian.com/migration/docs/compare-atlassian-cloud-and-server/ (Note that Server and DC…

That does not look like a message field to me. However, I do not know how message fields might work on requests, I've only used them on issues

Your understanding is correct. There are five ways you can grant access to people here: * Software and Core Licenced users: Can use the application (you can then do all sorts of controls with these users within the applications but the point here is that they) * Service Desk licenced users, or Agents: Can do most stuff…

Atlassian have stated they are not going to break the visibilty/restriction system in this way.

The url for an issue is <base url>/browse/<issue-key> In your system, you've got a fixed known base url (https://something.atlassian.net) so you can hard code it and keep it simple. In html, you just need to construct <a href="https://something.atlassian.net/browse/<issue key>">

It is as simple as removing the users from a group. Just go to Manage Applications and check what group(s) get access to Core. Then remove people from those groups.

Cloud systems do not have licences, you sign up and get a subscription that is free for a while, no licences involved. Server trial licences stopped being given out on February 2nd because Server is going away, and no new Server licences will be sold

Have a look at the built-in reports (in the project overviews) and then all the dashboard gadgets available. Jira does not really do timesheets, its work logs are aimed at issue tracking, not person tracking, but there are a lot of useful built in reports and gadgets that tell you a lot about the work being done and logged.

Try adding a "cascading select list" to your project. I think it allows for exactly what you're describing.

Read-only is not done on an issue level, it's done by project settings - either having a workflow that limits edit rights or by removing the permission from everyone on the project. Both of those affect all issues. If you do mean to do it to all issues (let's say in the "closed" status), you don't bulk-edit, you edit the…

You don't. There's no way to change the type of a field. You will need to add a new field of the right type, copy over any data you want to keep, and then delete the old field.

Not quite. The errors are being reported by Jira. That does not tell us the error is on the Jira side, it just says Jira has spotted the problem. The normal working procedure in your API call here is: * Celoxis makes a call to a Jira system * Jira uses SSL, so it asks Celoxis for some encryption stuff * Jira matches that…

The licence model changed on then 2nd of February. Team Calendars became part of Data Center and Cloud Premium, and the app for it was deprecated from the marketplace. You can still get it manually from https://marketplace.atlassian.com/apps/72307/team-calendars-for-confluence/version-history I don't think you'll see any…

There's no way we can tell you, I think you'll need to ask Meesw what organisation has taken ownership of their account (it's usually going to be the domain of the email - so if it's meesw@thingamy.org on their account, it's the atassian admins of thingamy.org)

Go to https://www.atlassian.com/software and click on each product, you will find links to their installer downloads and documentation on installing them. Note that the download pages will present you with "latest" versions, you will need to click on "older versions" to find the ones you've listed. Please have a read…

A good swathe of Adaptavist's clients have been Universities using Confluence, sometimes with aother Atlassian tools we've got involved with too. Server and DC so far, but a couple of the smaller ones are looking to Cloud.

You have somehow managed to put data into the resolution before you should do. The most common mistake with this is to put the resolution field on a create or edit screen. You should check over your config to see where the resolution field is presented to your users - the only place it should be is in a transition screen…

Ok, it looks like a classic project (sorry, I should have been more clear on q2 - Classic and Next-gen are the two broad types of project, software projects can by of either type. You can see what the type it is by looking to the bottom left near "configure project". Unfortunately the phrase "project type" is now a bit…

Ok, but 1) What do you mean by "template"? What are you trying to add to your project? And what type of project is it, classic or next-gen? 2) Again, what type of project? What is stopping you adding new transitions? 3) You can still search and order by fields in both Server and Cloud, what is stopping you doing it in your…

Slightly annoyingly, these are aliased as "raised in version" in the gadget config.

So this is pretty close: https://library.adaptavist.com/entity/automate-the-creation-of-an-issue-in-jira The adjustments you'll need are 1. to do it as a post-function or listener (depends on exactly how you want to trigger the creation of the issue - your question reads like you want to do it every time the field changes…

Hi Laci, This isn't an uncommon one, but the library doesn't yet have a script for this exact case. What we do have is https://library.adaptavist.com/entity/transition-an-issue-using-issue-input-parameters for doing the transitions, and if you replace the "find sub-tasks" loop with the "find linked issues" loop…

Start with https://confluence.atlassian.com/doc/upgrading-confluence-4578.html Clone your production down to staging and run through the documented upgrade procedure from those docs.

"Need assistance" is very broad. What help are you looking for?

One thing to quickly rule out - is your rank field really a rank? I ran into this a few weeks back, someone had added a number field and called it "rank", so it wasn't a ranking field. Confused the heck out of us until I remembered to check Admin -> Custom fields -> Rank and check the type of field. Could you check that…

Ahh, I always get screens mixed up, staring at the wrong one and thinking "it can't be this one". With Classic projects, screens are used in four places - View really is just the issue view, when you click on it and get it filling most of the screen, although it does kick into the pop-outs in some places. Create screen is…

That's fair, I often look at Jira, think "maybe a thingy that does this would help this client", look in the marketplace and feel utterly overwhelmed. Sometimes even just opening the gadget list is daunting. When I feel like that, I tend to simplify - go back to the client and ask for a problem statement (not even a…

I'm sorry, but it does. The comments are a lot of exposition on it, but that's the answer to the question.

It was the very first sentence in my original answer.