Nic Brough -Adaptavist- Expert

Everything, even the disk space consumed by the installation (although that is trivial and static). The data in the database is quite compressed or efficient though and the only thing you should worry about is attachments (of any type).

Yes, you can, the same way you use all the other REST APIs, and you get the token in the same way you do for the others.

Ok, my guess (as there's not enough of the error logs to be sure, but maybe enough from the pointers you have expanded on) is that you have a scriptrunner scripted field in the new issue that either * cannot be calculated as it doesn't exist for the target type * cannot be calculated because the target issue type does not…

You have not told us how you are trying to do SSL with the service, or what documentation you have tried to use and where you have got stuck with it. Could you describe what you're doing and where you got stuck with the doc?

You could renew the 250 and then upgrade to 500 users, but I really would not recommend that, it will cost you a lot more than the simple "buy a new licence for 500 users" and won't give you anything more. https://www.atlassian.com/software/jira/pricing?tab=self-managed for the pricing.

That's not how scripted fields work, they don't inject javascript.

Javascript is the wrong way to do this, even if you could get it to work. "The end goal is to call an external server that updates the issue with any changed status of the issue" is something you should be doing with webhooks or post-functions if you mean Jira needs to tell another server something, or the REST API if it's…

The gadget you've chosen is the one I would reach for. Do you have an actual problem with what it is showing you?

I'd say you need to do some work with your product owners and development team - just remind them that if they reject something, there should be a (brief) explanation of why it's closed as rejected. Worst case - take the passive-aggressive route of re-opening the issues and with "no explanation for closure" type comments.…

Eh? I said it's done with Scroll Viewport.

You're sill looking at the resolution field here. To change the options availble, you need to go to Admin -> Issues -> Resolutions and edit the list in there. Note that you should NOT make resolution mandatory. If you try to make it mandatory, you will have to set a resolution as you create an issue, which means that you…

What types of field are you trying to use for grouping?

No, there's no downgrade path for Jira data. What problem are you trying to solve with this?

And, no, deleting a project and then trying to re-use the key will not work. Jira does not completely delete projects, and you can't reuse the key.

That doc is telling you about how to have more than one ranking field, but it does not explicitly state something critically important to doing it - the "new rank" field is of the same type as the standard global rank. It's a ranking field, you won't be using your own field, just another rank with a different name.

You need to look at how you are doing this "move" to see where a script might be being used. I had assumed you were running a script (and hence knew where it was) because you only gave us errors implying it was a problem in a script.

Those are two different systems so "same credentials" is irrelevant. You'll need to check that the account on silabs has the right permission to log in and look at the server info.

Could you explain more? What are you doing, what is the error and what do you think should be happening?

I can use it fine. If you want help from us, you're going to have to actually tell us what the problem is.

There is no way to do this on Cloud

Could you show us the script?

The error means the account you are using does not have the right to see the results of the call. It might be that they're not authenticated, or it might be the internal permissions (I have a feeling serverinfo requires admin access to see)

You need to upgrade to get that fixed. It says 8.9 in the fix versions, so anything over 8.9 should contain the fix as well as 8.9

Atlassian are using Scroll Viewport to do that.

It doesn't. Sub-task estimates are not used in burndown. The time (estimated and) logged is not the estimate the burndown is working off.

This is what dashboards and saved searches are intended for. Try the two searches I list below, when you get a result for them, save them as a filter and give them a good name. Once you have some good saved searches, create dashboards, using gadgets that give you summaries of sets of issues (filter statistics for example).…

I think that might need to go to Atlassian support. I changed the setting in a Cloud system and saw it work immediately. Only guess I have is that it might be case sensitive (you've said DESC and the one that worked for me was desc)

Again, here. Head to the "jobs and careers" group you can find in the groups list in the menu at the top of the community pages!

Here, there's loads of us with a huge range of experience, many of us are here to help, as well as get help. If you want something more formal, maybe ask a partner or put out a job/contract advert somewhere?

It's not overwriting your filter, it's setting the rank. Moving items into sprints is ranking - they're the ones going to the top of the pile. In fact, if you create an empty sprint at the top of your backlog, you'll find you don't have to drag issues into it, you can drag the bottom line down to bring in the items you…