Comments
-
In global permissions, you can set what groups have admin access.
-
Correct, JQL finds issues. Projects do not have their creation date recorded, so even your SQL wouldn't work if you could use it. (the admin audit log gets a line, but those are transient - only kept for a while and cleared down when they're a bit old) The best you can do is look at "created" on the oldest issue in the…
-
How are you expecting to get this list into your user directory for Jira? (What directory are you currently using?)
-
Themes could mean a couple of things in Jira. Could you tell us which one it is by explaining what you mean by "theme"?
-
I am not sure why you thought you would get an email with a link, Confluence has always sent full notes on all modifications via email in line with what the documents say it will. It's the off-the-shelf behaviour which every end user expects. I've never heard anyone else expecting anything different, you're the first I've…
-
Do not start the service as root, it will take ownership of some of the files and prevent the "runuser" from using them when the service is started as them. I do not understand why you have messed with file permissions when I said you need to fix the permissions for the runuser in the operating system. Or why you have…
-
> teams cannot see their tasks and can redirect tasks among themselves That's an impossibility. If a team cannot see their tasks, they can't redirect them because they've no way to see them.
-
I don't understand - the Foxly field seems to be valid.
-
Yes, but you absolutely should not do it. Doing this will: * Render your Jira unsupported by Atlassian, which is a security issue as well as possibly a compliance one in many areas of business * Reduce the security of your system by getting users to write down passwords in plain text, use simple ones and reuse passwords…
-
For the versions of things to work together, see https://confluence.atlassian.com/adminjiraserver085/supported-platforms-981154553.html At a glance though, your MySQL server looks fine and Jira is unsupported on MariaDB so forget that. A 505 error implies the service is struggling with something though. Best thing to do…
-
My apologies for the delay, I've been struggling to keep up with all my email. The problem here is that you are not setting the resolution when you close issues. Jira has quite a complex set of ways of looking at closed and done, for historical reasons (seriously needs an overhaul), but as a result of it, we need…
-
There's no way to get more local - Frankfurt is your nearest Cloud server-farm. (Others, from memory are Republic of Ireland, Singapore, Australia and a couple in the US). So I am afraid you are stuck with the distance-related latency.
-
So the transitions are conditional, so they're not of any real use for reporting in the way that you want. You need to be looking at status, not transition. Maybe you should be looking to put the "analyse/estimate" request into the workflow explicitly? Have a transition into "needs analysis", then your developer can move…
-
Yes, the code bases diverged several years ago. Server and Data Center code is identical (we're nearly at a point where you can simply drop a DC licence into a Server install and all the extra DC functionality becomes available because it now thinks it's a single-node cluster!) Cloud is very different - if nothing else,…
-
Be careful here, you've said "Resolution status" which is totally unclear in Jira-speak because it is not a thing. Do you mean Resolution or Status?
-
Burn-down happens when an issue enters the last column on the board.
-
No, you never update the status in a post-function. To change the status of an issue, you use a transition. Embedding a status change inside a transition can only have two effects - it corrupts the data the transition is working with, or it goes into a cascade with a possibility of an infinite recursion (i.e. it'll pause…
-
You will need to associate other schemes with your projects, then you'll be able to delete the old ones.
-
The layout is not adjustable like that (you'd need to rewrite the code that draws this screen out)
-
Have a look at the workflow, to identify which screens are in use on the transition you want to set the resolution on, you'll be able to drill down into them from there.
-
That's a security setting on the operating system. You'll need to give your runuser the right permissions. This might be as simple as the groups that they belong to though. I usually do something like running confluence as a user called (say) conf, in group conf, and all the confluence directories and files are owned by…
-
Nope, that's the file generating it. Did you restart Jira after the change? And what do you now get in the footer? (After restarting)
-
Start at https://confluence.atlassian.com/adminjiraserver/upgrading-jira-applications-938846936.html
-
You'll need to show us more of the error, tell us what you have configured and things like the version of Jira and what database it is.
-
Ok, then your workflow has a validator on it that is looking for the obsoleted field, probably finding it by id rather than name.
-
Jira doesn't have any function that would allow for a pop-up create screen like that. You couldn't create the sub-task anyway - there's no issue to be the parent until after you've completed the creation of the main issue. Best you can do is an Automation (or script, or app that provides a post-function) that can create…
-
It's because you have the field "OLD" flagged as mandatory. Jira has no way of knowing you're intending to use XXX as a replacement for OLD, the two fields are separate entities. As well as removing OLD from the screens, you'll need to amend the field configuration to make it optional (and maybe XXX mandatory?)
-
Almost. I create page stubs all the time. Imagine you've got pages AAA, BBB and main. AAA and BBB live below main. On main, you put in [AAA] and [BBB] to link to those two pages, but you can also put in [CCC]. When you save the page, it will show as a link (in a different colour to indicate it is a dead link) and when you…
-
I'd agree - I use that all the time to create stubs - pages that don't exist yet, but I need to write later, when I'm done with the current page.
-
The / can be used instead of { to get to macros and some other shortcuts, but I can't find anything for link to another page.