Comments
-
Eh? It's their data, not yours. It's up to them to reassign issues if you leave. And I would need to retain the detail of who did what, so although I'd disable your account, there's no chance I'd remove it.
-
Your Jira is using SSL, but your Confluence does not have the certificates it needs to talk to Jira over SSL. Your Jira (or the proxy in front of it handling SSL for it) can provide the right one (you can save it from the browser), then you'll need to get it installed in the Confluence's Tomcat.
-
Welcome to the community! You can put many status in one column, and/or remove columns. The key here is to simplify what you've got.
-
You will probably need to talk to the administrators of your system. We're end-users here, not your admins, so we have less access than you do!
-
No, again, it's the ' marks, not s. Although your header line is also incorrect, missing letters
-
It won't. There are too many different ways to measure progress. Plus, you do not put Story Point estimates on sub-tasks.
-
I am afraid you have not given us any description that might help us work out what the problem might be. What macro error? What is the macro in use? What is the pattern? (always fails on every page, intermittently, by user, by browser etc)
-
Have another read of my last paragraph. It's not that it would not be useful, but that you would have to rewrite EVERYTHING in Jira that works with the results of a search in order to show it to the users.
-
No, and you should never be sending a username and password over a url! You will need to use Oath to do this.
-
Your database was not set up correctly as you installed - probably the user didn't have all the rights it needed. The errors you are seeing are about missing tables (specifically Bandana), which would always be created on a successful install. I'd want to check what is in the database you configured - any tables at all?
-
It does look odd, and it's that way because you also have groups to check in restrictions, and that becomes a bit of a pain. Atlassian have not really tried to fix it.
-
You'll need to explain what this has to do with Confluence?
-
If you don't have Service Desk, or want to do this with non-Service-Desk projects, start with the built-in email handlers - https://confluence.atlassian.com/adminjiracloud/creating-issues-and-comments-from-email-779288896.html
-
They arrived over a year ago. They are tied to each project and created automatically.
-
I can't say that I have a "favourite" animal, there are so many I could write glowing reports on. But I think I'd have to pick out the family we know as "cat". For evidence, have a look for pTerry Pratchett and Gray Jolliffe's "The unadulterated cat". If nothing else, the explanation of how almost all other animals evolved…
-
Mmm, the reason I say it's useless is that ranking a subtask outside the parent is wrong. If you have a sub-task that should be ranked over another story then there's something wrong with your ranking. Either the sub-task is on a story that is ranked too low and needs bumping up, or the sub-task is something that should be…
-
Creating a space is not something you do in the database, and you certainly don't need (or want) to drop any tables. To create a space in confluence, log in as a user who has "create space" permission and click "create space". If you think that is wrong, could you explain what you are actually trying to do in this dev/test…
-
My guess is one or both of: * The status at the end of your workflow is not in the "done" column on your board * The issue has one or more incomplete subtasks (an incomplete subtask is one that is not in a status that is in the right-hand column as well)
-
Start at https://confluence.atlassian.com/kb/health-check-thread-limit-858578685.html
-
It's a bit difficult because your backlog is determined by several things, and you need to add them together to get it out in other places. I would * Copy your board's filter as the starting point. That will cover your backlog, but also (probably) done issues and stuff already in sprints. * Add a clause to it to match…
-
Hmm. You'll need to use a mail server that does not need SSL then.
-
There's no way to inject things into the Clone screen - you need to find or write an App to do cloning the way you want (and turn off the built-in function if you want to force people to do it with your code)
-
You cannot go direct, there are known problems if you skip upgrade steps. You must go from 6.1 to 6.4, then to 7.0. I am not sure if there is a minimum recommended 7.x version to take to 8.0 yet - it's not been around long enough! (It took quite a while to find out that if you went from 6.4 to 7.10+ direct, you ended up…
-
There's no way to re-arrange task numbers (and even writing something to try to emulate it would make a right mess), but if you use Jira Software, you can rank them all in the backlog
-
No, I used 's to mean the plural of ' You should remove most of the ' in your command and use " instead, as your OS is getting it wrong.
-
Repeating the original question, which has already been answered, does not help explain what you are looking for Please could you explain what you think an "injection" might do? As explained already, JQL is not SQL, and not susceptible to what security systems call "SQL injection" attacks. To try to rephrase it again, even…
-
Sorry, I was unclear, and left one thought out - you should be able to do this *eventually*, when the function is added to Next-gen. For now, you can't. It's just the way you should be able to do it in future if I've read the conversations correctly.
-
You don't need to think about "security patches". You need to upgrade from 6.1 to 6.4, then to 7.0 and then 8.0. The new versions include things people think of as "patches".
-
Atlassian measure that by looking at the votes and volume of comment on the main bug. i'm not sure I'd bother with a badge that says "I have this bug too" - I'd only really value the new bugs I'd not had before. But it's always worth voting on bugs to tell Atlassian you're seeing them too.
-
It's hard to tell without knowing where you are seeing this error, but my instinct is that your mail server is using SSL, and your Jira server has not had the certificate imported (the one that tells the mail server that the jira service can be trusted)