Comments
-
Ah, yes. It's quite small on my android, but it's still a waste of space and the css should be improved. For an iPhone, we've used https://marketplace.atlassian.com/plugins/com.atlassian.jira.plugin.iphone.jira-iphone-web-interface but that's only for 4.x I think you'll need to fiddle with some css to improve this. I…
-
You might want to tell us which application you're talking about? Also version (and theme if it's confluence)
-
Sorry, I missed this earlier. The problem I've got here is that it looks like something on your network - other people (including me) have no problem submitting, but your "spinner" implies that something is blocking the send of data to Atlassian. There's not a lot else we can do here, beyond trying to raise it from another…
-
I'm afraid we're not support, and although support may watch here, they may not see this issue. When you say "does not send", could you give the exact symptoms and how you know it's not been sent?
-
No, the pricing is very different. See https://www.atlassian.com/software/jira/pricing?tab=cloud Contact https://support.atlassian.com if you switch part way through your server licence, they can help you move the licences over to Cloud.
-
>com.atlassian.confluence.core.InsufficientPrivilegeException: User admin does not have the required privileges That implies you are trying to add a user from an account that can't do it. The UI won't actually let you get that far if your account doesn't have the permissions, so I suspect you are bypassing it and using…
-
Nope, not if I understand your question. I think you're looking for https://jira.atlassian.com/browse/GHS-9741 ?
-
Yes, I was assuming that the poster knew how to work out a connection string.Anyway, Rodrigo beat me to the answer (and you usually find the string in the .cfg file will contain :3306 in it, which you just change to 3307)
-
Go into the *source* project and have a look at its configuration. Look for the "permission scheme" and descend into it. In there, there is a line that says "create issue" with some rules next to it (such as "group: x, role y"). The easiest thing to do here is an explicit brute force change - add "group:…
-
You need to ensure that the permissions are set up so that when you clone the project, you will end up with "create issue" rights in the target project.
-
It's not a standard post-function, so you need an add-on to provide it. I suspect Kian has the right answer.
-
Something is stopping the system plugins from loading - sometimes this is resources on the server (you can increase the timeout, or give it more memory), but as you're writing an add-on, it suggests it's your add-on blocking the others. Read further back up the log to find out what loading your add-on is doing.
-
JIRA Software does not do anything with estimates on sub-tasks. Plain JIRA rolls them up and displays the estimates and worklogs on parents, but they don't have any role in Software.
-
Jelly was removed a version ago, let alone 7.But we don't update answers - they're answers to questions, not documentation.
-
Yup. Set up the workflow as above, then write a filter that says "status = awaiting client and updated < -30d", then use a jelly escalation script to trigger the close transition. See https://confluence.atlassian.com/display/JIRA/Jelly+Escalation
-
I suspect this question is actually one about automation. This crops up irregularly because it's not obvious that Status (of an issue) is NOT a field, it is an indicator of position in the workflow. Developers keep adding post-functions to Jira that say "in this case, change the status", without understanding that the…
-
Yup, use the REST interface. See https://developer.atlassian.com/confdev/confluence-rest-api
-
Er, why would you expect to have "assign"? You don't know who is best placed to do the work, what sprint any work might go into, or even what team it's going to go to. As a user, you can create bugs. It's nothing to do you with you who the developers are, until they're chosen by the team.
-
Ok, that's good because it's clear, but potentially complex because you'd need to read the entire permission scheme for every rule.I'd dodge that and just look at the "browse" permission in the scheme if you need a simple view - it's technically wrong, but it's rare that you'd have a user who can do things in a project but…
-
Depends on your user directory, but there's no easy SQL to get it even in the internal directory. First, what do you define as a "user of a project"? Someone who can see it? Or someone who can create issues in it? Or they can be assigned issues? And so-on. Then you need to read your permission scheme to find out the rules…
-
Yes, very soon.
-
It's the latest version. I think Atlassian have removed the version information that used to appear in the footer, as it's not that important beyond "latest". It's usually several point versions ahead of the server releases if that's what you were looking for.
-
I think one of your colleagues may already have asked - https://answers.atlassian.com/questions/16881621
-
There's quite a few improvements to voting requested on Atlassian's Jira, I suspect some of them would get you what you need. But there's nothing built in that would do that. You'll need to find/write a plugin to do it in Jira
-
Do you mean you have a local network that is not exposed to the internet? An intranet? JIRA runs fine on intranets as well as the internet - it's a web application you can run over any network you want.
-
Ok, I'm going to answer this backwards. 2. Never, never, never point two Jira installations at the same database. By all means, copy it and run it somewhere else, but do not use a single instance. (You wouldn't want your test data polluting live anyway) 1. Depends on the database you are using. I'm afraid that's a bit…
-
Septa has covered most of what you need to know, but I'd like to add some quick tips. The usual process for creating a test system is to copy a production database to test and point your test Jira installation at it. If this is the route you take, then there's a handful of things to worry about: * The licence - as Septa…
-
Yes, I think just removing the jira-users group from the role will fix it. The cross-project mailing made me suspect it was a simple group usage lurking - I've lost count of the number of times I've kicked myself for forgetting that groups can be added to roles as well as individuals...
-
I'm not quite sure what is wrong here. It is complex, but it is very logical, and it's doing exactly what it should do. Your notification scheme says "notify users in role A when issues in the project are created". Note that it does NOT say "in project A", it really does just say "users in role A get created mails" If…
-
I'd read https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html