Comments
-
It's not clear what changes you want to make here are. Best guess is that you just need to add a new custom field for the "list" and make it mandatory.
-
It's the same answer - there's something wrong with your network or client if you can't render the page. However, 5.2.4 was pulled because of a bug that makes it corrupt data, so you should be looking for a different version.
-
The rest of the networking system. If the service is working on localhost, but not on the hostname, the networking is blocked. It might not be a firewall. What is the error message?
-
Jira does not natively restrict sub-task creation like this, so you'll need to focus on whatever add-ons you have that may be removing your access.
-
It's running out of memory. In a lot of cases, memory allocation is complex and throwing more memory at it is not immediately the right answer, but if this is crashing just on the licence, that is the first thing to try. Change the setenv.sh file to allow it more memory
-
We can't see that, let alone escalate it. You'll need to chase on the request yourself.
-
This sounds like you might want to synchronise between copied projects in each Jira. I'd recommend a look at Backbone and Exalate in the marketplace.
-
There's no way to do this on Cloud, although batched emails are coming to Server 8.
-
As the others have mentioned, you will need ScriptRunner or some other form of automation to do this. You could do it with validators, but you are likely to find "I can't move my issue until I've edited and then changed something to match" is quite annoying for your users. I would try: * Create a select list to be used as…
-
It is about training, yes, those who are re-ranking should understand that when they move issue A above B, it is a logical necessity to rank A above everything that is between A and B, even when that is not currently visible to them.
-
The fields are locked for a reason - you should rarely have any need to unlock them. If you're on Cloud, there is no reason that doesn't mean "Atlassian should handle it". On server, there are some, but you need to be very certain that you've run into one of the bugs that requires it.
-
Not directly, because boards are not containers for issues. There's no "move from board to board", it doesn't happen. Boards select a set of issues to display with a filter. An issue is on board A when the filter for A selects for it, and it's on B when the filter for B selects for it. When you change the data on an issue,…
-
You can't do this in full, as there are two layers of permission to view an issue which simply don't support it. * Layer 1 is project permissions, where you can either see all issues in a project, or you can not. * Layer 2 is issue security, where you can hide individual issues by setting a field. But sub-tasks take the…
-
Sorry for the delay, I didn't see the response. The workflow scheme maps one or more workflows to the issue types in your project. Often, there is only one in there, so all issue types use the same workflow. Can you check the mapping in there? It should say just say something like "All issues use workflow X". If it says…
-
Hmm, that's an interesting one. 12c explicitly has an equivalence between "Create Session" and "being in the Connect role" and you have that set, so it should be working. It should not be giving you the error you are seeing, because Oracle should be letting it in. I think this one might have to go to Atlassian support…
-
Very hard to say without a detailed look into your feedback needs and whatever a VOC is ("Volatile organic chemical" springs to my mind, but there are two biochemists in my immediate family) At a stab, I would say a simple Core project would cover the basics. A simple workflow, with a handful of fields for capturing the…
-
Well, I'm afraid that's vastly wrong. * I do not work for Atlassian. if I did, you'd see less opinionated stuff, a lot less criticism, and longer more detailed answers as I reigned in my "<sigh> RTFM / LMGTFY" instincts more. And I'd be booted off the community for lying about my employer. * I rarely "kick the ball down…
-
Please read the previous comments before. You have made most of the same incorrect assumptions and mistakes as the others before.
-
You can't do this directly. Behaviours can do the show/hide, and require/optional, but the choice of whether to show a screen is out of your control, as is the display of parent issue. But you can do those indirectly: * Create a scripted field for "parent issue type" and use that on the screen * In the workflow, have two…
-
JaC (the "development jira" you mention) is running on Server. The new UI is only for Cloud and you can't use the old layout on there any more. The only recommendation I can give you at the moment is to move to Server (whether hosted yourself, or by anyone other than Atlassian), as that will not be getting the new ui for…
-
Again, Jira Ops is not going to be implemented for server for a while. It's going to get going on Cloud before Atlassian think about a server version. The migration to Cloud can be tricky - see https://confluence.atlassian.com/jirakb/migrating-from-jira-server-to-jira-cloud-779160826.html
-
Ok, if you can't connect to localhost:8090 and you can see Confluence running on port 8090, then either your hosts file is totally messed up, your networking on the machine is incorrectly configured for routing, or your server is still running a firewall or routing system blocking even local access.
-
I'm not too worried about Chrome connections, I think we know they're failing. What exactly were the errors you got from the first two wget/curls I asked for? The ones physically on the server?
-
I'e found the Atlassian docs to be completely linear, and they work most of the time. The problem we usually find here is that someone has skipped a step or got something wrong, then gone off-story trying to fix it (there's not a lot you can do about that - troubleshooting installs can be very very long, and you don't want…
-
As a raw test, try the IP address of the server instead of the host name, that eliminates any worries about routing and naming.
-
Most Apps will log to the application log by default. So have a look at the main Bitbucket application logs.
-
Ok, so is Confluence running on port 8090? Is it running at all?
-
You mean change status - issues do not have a transition, they are actions that change the status. Anyway, the error message you are getting is clear. Your action is to transition from one status to another, using the transition between the two that has an id of 21. You are giving it the a field, but that field is not on…
-
It should be nothing to do with localhost or testing - there should be buttons after the radio-buttons that you can click after selecting one of the three options. Could you try refreshing the page? A different browser? Are there javascript errors anywhere?
-
Connection refused is usually caused by one of the things you've mentioned, so I suspect there is still a firewall or configuration in place that is blocking the confluence port on the new IP address. Or something is not running. Assuming that Confluence is running on the default port of 8090, can you try * A simple wget…