Comments
-
This defeats the whole purpose of having a workflow (and hence a board representation of the workflow). Your "ready" flag represents a step in the process, not a field, so you should reflect it in the workflow.
-
The problem with this is that whatever database you are connecting to is telling Jira that it is set to utf8, not utf8mb4. Why is it reporting it like that?
-
I'm afraid your only option is to include the same version of the library in your app. (or if you know you're going to always use the other app, don't include it at all)
-
Can you confirm that when you say "java developer", you do mean just a JDK? If it is just a JDK, then you'll need to look at how you installed it - if you used a package manager or installer, it should be removed using that. If you did it manually (download an package, decompress it somewhere), then all you need to do is…
-
Yes, you've handed it over to an organisation. You are no longer the owner.
-
This sounds like you have not added a new "ready for test" status into the workflow for the issues, and mapped it into the new column. It could be a number of other things though. To work out which one it is, we need to know a bit more about the config (workflow and board settings)
-
No, it doesn't remove the option to delete your Atlassian account. It just makes your system stop using Atlassian accounts for access and start using GSuite instead.
-
I think https://library.adaptavist.com/entity/set-the-value-of-date-or-date-time-fields might be able to do what you need.
-
Yes, that means email is being sent and received. I think we could do with a view of the rule(s) that say your "same email" should be notified (similar to your screenshot for roseceshi - but two copies - one when they're not getting email and one when they are) However, there's one other thing to check - can the user see…
-
The minimum back up set is actually just Database + Attachments (or the data directory that contains attachments in some systems) - the rest of the home directory is not strictly necessary. But having a copy of it makes restoring a system a lot faster and easier.
-
That suggests that while the user is logged into Confluence, they are not logged into Jira.
-
Yes. There are loads of sample scripts for looking at linked issues at https://library.adaptavist.com/search?term=linked
-
Yes, that's what project categories are for. See https://confluence.atlassian.com/adminjiracloud/adding-assigning-and-deleting-project-categories-844500732.html (it's a simple scheme though, you can only put a project in a single category)
-
Cloud does not have a framework that allows for the injection of the code that could do this.
-
This suggests your notes field was not valid in the project you moved to. When that is the case, Jira has no option but to lose the data that was in the field, because there is nowhere for it to store it. This means that yes, your only record of the data that was in it is the history record. You'll need to make the notes…
-
Yes, you can remove all the links to download a file and make the url its available on inaccessible. This, of course, makes the file utterly useless - the end user will be able to see that there is a file there, but not open it with preview, or read content out with macros, or render it on a page.
-
It has to - the link you are getting is to download the file created by export.
-
What do you mean by "get the data" and "subscription"? User Activity? Issues assigned to them? How many penguins live in their house? Subscription to filters? Your Cloud system? Penguin weekly magazine?
-
There is no "automatic delete" - the only way to delete a service desk is for a human to click delete, (or not pay the bill so the entire Cloud system is removed) One of your administrators deleted the service desk (or possibly moved it somewhere else?). The administration audit log should tell you who did it, There's no…
-
No. An Atlassian account belongs to the person, not the organisation. If someone wants to delete it, they're entitled to. All the organisation can do is point out that if they delete it, they won't be able to use the systems that they probably need in order to do their job...
-
Start with the administrators of the system being abused. Although if it is them abusing it, report it to Atlassian at https://support.atlassian.com/contact
-
That really is what it says - the server tries to connect to the database server and gets back "no". Could be a network issue, could be that the database server is configured to not listen to the server. You'll need to debug those two problems.
-
Possibly. A new project is separate from the old, but does not affect licencing. What matters are the people using it. If Alice, Bob and Charlie are agents in Project-1, then you need three agent licences. If Alice, Bob and Charlie are agents in Project-2, then you are fine - you have 3 licences because they're agents in…
-
I'm afraid the (very very very basic) voting system in Jira is pretty much part of the core and the only way to get a better one is to use an app to do it. You might be able to do something in workflow, or even outside it, but it would need coding itself. With Scriptrunner, I've implemented a very very simple, but slightly…
-
I am sorry, I do not understand most of that. If you add the issue type "feature" to Jira, you can then enable it in any project you need it in, by adding it to the issue type scheme for the project. I have no idea what you mean by "filter from the other side"
-
You will need to talk to your administrators. We can't help you with this, we are a Community of people here to talk about Atlassian. Your administrators may be active here, and see this question, but this won't be the place to ask them for support such as this. I suspect you have landed here because you clicked on a link…
-
The database does not appear to be set to utf8mb4_bin - in the result line, it is reporting what the database has told it the collation on the Jira database is. You'll need to change the collation of the data, as well as the database setting.
-
Ok, you'll need to follow the guide in https://docs.microsoft.com/en-us/sql/relational-databases/collations/set-or-change-the-server-collation?view=sql-server-ver15
-
Well, sort of, but you need to buy licences for the QA and Developer server before anyone is going to help you.
-
Partly. You are breaking the law by using the licence for three systems. If the QA and Dev instances are for developing and testing Jira code and configuration, then you should be using a developer licence for them, and you would not need or want application links between them and production. If they are for issue…