Nic Brough -Adaptavist- Expert

Welcome to the Atlassian Community! Nope, this is something you do at the operating system level and I don't know what you're using for the server. Changing ownership of files is a simple command, but you'll need the server admins to check if this is the problem, and change the ownership. They'll know how to do it.

Welcome to the Atlassian Community! The most common reason for this happening is that you are using a MySQL back end database and it is not set up to support certain characters. Your user may be trying to copy and paste, or somehow else insert and advanced emoji (the one I ran into first was the poop emoji). Check what…

I am not sure I understand the problem you have here. Confluence has two types of comment - I currently call them "inline comments" and "page comments", but I really like your choice of "detached comments" - the page comments are clearly detached from any content, only referring to the whole page. But I think you may have…

A quick thought - custom fields generally apply to issues in projects, not the project, so "project manager = currentuser()" could easily return a LOT of issues within assorted projects. It would work, but have ugly results. But, projects can have project leads, so "project in projectsLeadByUser()" might help if you're…

Welcome to the Atlassian Community! You are exactly right - the upgrade simply scrubs all the existing files, so you lose all your customisations. Atlassian could be a bit more clever in their upgrade code - if a properties or xml file is in a standard format and the changes you've made to it not too extensive, then it…

The string you are seeing there is (probably) a unicode 4 byte encoded character - these were added when we ran out of space in the 3 byte scheme. You usually see them in more recently standardised Emojis. Sadly, I learned this the same way you have - trying to prep an upgrade, Jira issues were going missing, finding a…

Yes, you can't actually delete schemes if a project is using them, archived or not (well, some you can, but you have still migrate to a new scheme if you do it) When you archive a project, have a think about how you were using it, and why you're archiving it. The schemes determine how a project works in general, but do you…

That's pretty much the answer I would have given if you hadn't got there first! There is no "move", it's "add it to the new group, remove it from the old", and there's nothing built into Jira to do this en-masse. I too would recommend a look at the REST API

Technically, yes, you could take an issue from a JSM project and move it into a development type project for further work, but there's a big problem with doing that - you'll lose the request the customer made, and your communication channels with them. To the customer, it looks like you've deleted their request! The right…

First, I'll want to be open about my opinion - it's "meh". I don't often use Community on devices that don't have a decent-sized screen and a keyboard, I wouldn't bother to install an app for it on my devices. (The handful of times I have used it on the 'phone, the browser has worked well enough). Also, I don't use a…

The only "fix" for this is to not use team-managed projects, or at least, don't try to report on them with the affected gadgets.

You say "The workflow was built in the project under configure/edit workflow.", and it's shown in your screenshot too. Both of these suggest you are working in a team-managed project, which do not create workflows, the workflow is done all inside the project you build it in. For an issue to be considered "done" by most…

You'll need to take that up with the vendors of your TV.

Ahh, that explains it - this is a customer account, not a Jira user. You'll need to add them back into Jira - it's reporting "disabled" because it is finding the customer account, not a Jira account, and assuming that you have deleted the Jira user that was there before.

Ok, so you'll need to get your administrators to work together on standardising your projects and not letting people diverge away from the standards.

I think we need to see the raw data - could you search for the issues in the done column, and show us the list - Issue type, issue key, and the estimate field are the only three columns we need to see.

We can't help you with that - you've not told us what you have got set up in your database, and we're not R coders. (If you are talking about writing data into Jira's database, then stop and redesign your project - you should never write to a Jira database)

Eh? "How is a mere user of Jira able to find the names of the fields so he can run a query?" - why would they be looking at a list of fields to find out what they want to query?

Yes - I do see a lot of uses for the macro you really want to have here. I'm not an Atlassian, I have no say, but I do want to ask them for so... many... improvements. And this is one of them. Anew macro really feels like the right answer here. (FWIW: I don't think Atlassian would ever give me a job, I don't think they…

Which "web links" are you talking about?

The problem here is that you have got a story that is in an inconsistent state, and Jira can't know what to do with it. By definition, a sub-task is part of its parent issue, not a separate item. You have told Jira that BCN-1218 is done (by moving it into the last column on the board), but equally that it is not done,…

Have you asked them to try logging into your Jira Cloud site? And then logging in here with the same account?

Welcome to the Atlassian Community! This is something we can't really help you with. You are working with Jira data, yes, but you've copied it out to your own database, probably in a different structure, and you're using R to query that. A lot of us don't know R, and none of us know what structures you have built in the…

This rule may change in the future, Atlassian have been promising custom urls (i.e. not xxx.atlassian.net ) for years, and if they deliver, it'll change. If you are unsure, reach for "help -> about" - belt the help question-mark at the top right, and look for "about". In some cases, it's right at the bottom of the panel…

Welcome to the Atlassian Community! Technically, it's really up to you how you choose to implement your hierarchy So, historically, Jira Software has implemented only three layers - Epic -> Issue -> Sub-task, and you can have many differently named issue types, and sub-tasks. That obviously translates into Epic -> Story ->…

It's already been done, but as a distinct product, rather than a group. See https://community.atlassian.com/t5/Atlassian-Automation/ct-p/automation

I don't know, what is the code in your plugin doing with the workflows?

Company managed projects are not going away. A lot of us restrict or even disable the ability to create team-managed projects.

Um, how did you get to it, if you didn't search for it?

Your release type is already a custom field, I think. Go to the custom field list, find it, and click on "configure" instead of "edit" - that will take you to the list of options for it, if it is a select list.