Nic Brough -Adaptavist- Expert

Space permissions is not a "feature", it's an integral part of the administration of the space. Why would you want to move it out of the space administration menu? But to answer the question, no, you can't move it out, the menus are coded to meet a sensible design pattern. If you have an app that can inject inject…

Use the process manager on the server to see what is running. 

"Audience" is a great word. However you are talking, "know your audience" is the best advice ever. Your audience might be millions of people (like typing stuff into the Community here), or it might just the three people you live with. There is something about clarity that matters, whatever the audience. Everything I've…

Welcome to the Atlassian Community! It's always a good thing to have a person responsible, that is exactly why the assignee field is there and is a single person. I am not sure about the rest of your question, but it hints at having sub-tasks (part of the original issue) that help you break it up into more manageable bits.…

Today was very much an edge-case. Emojis are a lot older than most of us, and the basic ones are well understood. The problem I see is with the proliferation of unclear ones. Frankly, I'd take them out and burn any emoji that you can't put in front of any one of the (almost) 8 billion people on the planet who are old…

So, I had rather an interesting incident today. I'll try to keep it short * Bob posted something with a bit of an emotional load yesterday (in a channel intended for mutual support, so absolutely the right place) * Charlie responded with an emoji * Bob came to me, highly upset about it, to ask for help and ask why Charlie…

It's not the server that is creating the database - you have to do the basics, getting to an empty database that the server can then add things into.

Ahh, of course. On top of that, Done issues won't appear in a backlog because a backlog is only for looking at issues that need work, and sub-tasks are pointless noise in a backlog, so they're hidden too.

Do the first 500 (highest ranked) ones show?

The script would have no cost, but it was for DC/server, so it's not workable on Cloud, you would need a different approach. I'm sure SR for Cloud can still do it, but my server script won't help you much. Start at https://docs.adaptavist.com/sr4jc/latest/features/scripted-fields

Yep, that's exactly how I did it. Specifically a scripted field with a numeric template and number-range searcher, and a script that took the lexorank values and converted the text with a primitive algorithm. It's not pretty, but at least it's sortable and comparable. And visible.

I didn't say reboot (I assume that means you rebooted the server?), I said stop Bitbucket and make sure all of it is completely stopped, before restarting. Rebooting the server will do that, but it might also be restarting Bitbucket (and Elasticsearch) as it boots, which would explain why you're getting this error when you…

If you go to configure a request, you'll find it can map the customer request status on to the issues behind it. Imagine a simple case where your customer service team has to do several things to get a request fixed. You may have a workflow that represents that process as: New -> Under investigation -> develop things ->…

It uses Automation, which is installed on Cloud automatically, but you will have to add the full app to Data Center (not the "light"/free version)

Thanks! I was curious as to whether it was a real rank field, or just a rating field (not a criticism - rating type fields are a good way to help prioritisation and feed into ranking if you're using it. I was curious if you had done it the way I have - written scripted fields that convert the rank to a simple number so…

Repeating what you said already does not answer the questions. There's a reason I asked them - we can't help you without a clear definition of what you're trying to do. Best we can do at the moment is link to the script I gave earlier.

You can do this with a bit of modification to the script I've pointed to. But you still haven't told us what you're trying to do. It's clear that you want "issue create" to spawn a load of sub-tasks, presumably on the issue being created, but what are the rules for deciding what to create? A fixed list of X items? One per…

Is that field being calculated from the actual rank field?

The error message tells you what the problem is - it's already running. You'll need to look at doing a full shutdown of Bitbucket server, checking that all related services stop correctly, then start it again.

No, there's no access to the logs on Cloud. The best you can do is a look at the built-in analytics, which can tell you how much pages are being hit wth browsers and rest calls reading them.

I'm afraid it's still the other way around. Bitbucket does not deviate from any standard in its field, the problem is that a client does not support the service-specific stuff. It is the responsibility of the client to adhere to the standards as well as the service, but also the responsibility of the client to support the…

There's an example of creating a sub-task at https://library.adaptavist.com/entity/create-a-sub-task-and-link-to-parent-issue-in-jira But I'm afraid I don't understand the rest of the (cut off, I think) question. My guess is that you have a parent issue that has one or many values selected in a multi-select field and you…

Yes, you shouldn't need to amend anything else in Jira if you're using an outgoing proxy.

Welcome to the Atlassian Community! You're going in the right direction. On question 2: Yes, transitions. You can not just set an issue status, it's not really a field, it's a display of where the issue is in its lifecycle. (You can actually code something that will change the status directly, but if you do, all that…

There is not a lot we can help you with here. This problem is entirely one of your network, not Jira. You need to configure your network to allow Jira to reach the marketplace.

I understand that. "How do you suppress them in the list? " Take away people's right to edit issues in the projects you don't want to see.

Welcome to the Atlassian Community! You'll need to talk to the administrators of the workspace that is being abused. If the whole site is abusive then report it to https://www.atlassian.com/trust/report-abuse - ideally forward one of the emails.

None. Well, microseconds, not that we humans will be able to tell. Jira does not cache permissions, it always reads from the database. So I suspect you might have got the permission wrong or granted it to a different account than you thought you had.

Why would a display name have any effect on how a thing works? Have you tried taking away people's access to edit these projects?

So they are not really "dead"? Because people can still use them?