Nic Brough -Adaptavist- Expert

This can't be done. The customer and agent portals are the same thing.

None of the cascading select lists I've seen support this. There are some (non-atlassian) systems that I've seen fields do something that sort of works but I have to say that they seem to confuse people unless the data selection sets are incredibly simple (in which case, it's generally better to use separate fields).

The cog icon will only appear if you have administration rights in the area you are in. For example, on Cloud, I get: If you're not seeing the settings cog here, you'll need to talk to your admins about getting the right pemissions

The original and remaining estimates are really part of the same (complex) field. You don't just edit them, you need to use the work log functions to record or adjust time in them.

What type of field is the Area?

What do you mean by zLabels? Do you mean a custom field of type "label"? What are you expecting a "revert" to be?

What are the errors you are getting?

I would use a simple filter that includes "order by updated". Filters are usually displayed in the "issue navigator", in which you can choose what fields to display. You'll want to get "updated" added to the display.

This happens mostly when you are using an unsupported database version. Can you check your version of Confluence's "supported platforms" page?

This is not quite a "bug", but definitely a design-flaw in Jira Software. Sub-tasks will always be in the sprint that their parent is - Jira does that right in most ways. But failing to tell us humans what sprint a sub-task is in, no, Jira doesn't do that quite right.

You are trying to set up your everhour system with a url that is already in use by someone else. You'll need to choose a different url (or go into a lot more detail about what you are doing and explain whet you think is wrong here)

No, don't use SQL to do this, you'd need to write a complex macro to get it to run every time you refreshed or visited the page, and the SQL would be inefficient. Why don't you just use the Jira issues macro?

Have a look at https://library.adaptavist.com/entity/create-a-backdated-issue - it does some work with dates as well as creating an issue.

If you have one of the automation or scripting apps, then yes, you can automate that.

This suggests you have something automated on issue create that is breaking the index.

You should issue a REST call to transition the issue from one state to another. See https://developer.atlassian.com/cloud/jira/platform/rest/v3/?utm_source=%2Fcloud%2Fjira%2Fplatform%2Frest%2F&utm_medium=302#about

What do you mean by "workflow dependencies"? Fields are mostly not limited by user (exceptions are a few of system fields - you can limit due date, assignee and reporter edits to project-roles, groups or other roles). If you want to control access to other fields, you either need an app to limit access, or you need to move…

No, you cannot have two assignees for an issue. If you want a secondary/backup assignee who is less responsible for the issue, you will need to add them as a participant, watcher or into a custom field.

This suggests that the proxy cannot get a response from the server behind it. I'm afraid we can't help you with your networking - you'll need to debug why your proxy is not getting a response.

This is a bug in Windows - it fails to recognise that just because a service needs a directory to be there (and hence held "open"), it doesn't mean the files in there are open. There's no easy fix for this, other than stopping Jira so that Windows doesn't see that "lock". 

This is just the current display, before it has been created, it can't know what the new number is.

They have a bit of a problem with this - no-one will explain what the install problem is, because when they run it as instructed, it works. Please could you tell us what the actual problem is and what you are doing?

404 means the server is not there. Check your network and if the server you are trying to connect to is running ok.

I am not sure how it is incorrect behaviour to not do something you should not be able to do. You have an issue that you have put into the wrong status. It is not complete, because it has open sub-tasks, so it should not be in the "done" column. Move it back out of the "done" column and it will work fine.

Thank you. 

Actually, no, it doesn't. It allows people to use your filter to find things and then edit their own version of it. They can't edit your filter, just create their own. You really don't want to stop them doing that. An issue tracker on which people can't search or run the reports that they want to is not a lot of use.

No, the boards display issues once. It would be a nightmare to have them duplicate cards.

This sounds like the Great Firewall is blocking access. There are no bugs in Jira related to this - it simply sends email. If there's a fault sending, it's not with Jira.

Please read the post yourself. Not just my answer, but your own question. The error message is telling you what is happening.

A cloud system will usually be set up in the data centre nearest to where the request to create it was issued. In Sweden, this will almost certainly be in the Republic of Ireland. To be certain of the location, I don't know of any way to be 100% sure without raising a support request for Atlassian to check it for you.