Comments
-
This is a problem with your process set up - you will need to be calling the ssh process with -t and -T as well.
-
Roadmaps are provided by the advanced roadmap app. You either need to subscribe to that, or get a premium account to enable that.
-
I think you'll need to start by explaining what you think KCS is. Given that it means "Kings College School" or a stationary supplier to me, I think you can probably understand that most people don't know what you're talking about
-
No. There are no downgrade paths for Jira, if you're on 8.7, you can't go back to 8.5.
-
I think they dug up the app or config that was making the change and shut it down.
-
Because the target type is configured differently to the source and hence the old data is not valid for it. You need to look at the configuration of the fields as well as the projects. If the possible values for the fields were the same, you would not be asked how to change the data to match the new configuration.
-
You will need to upgrade your MySQL service to 5.7. The missing mysql.sock is down to MySQL not being installed correctly. I'm afraid we can't help you with that, we don't know what is wrong with your installation.
-
I'll start with "grumpy-nic" - no, I can't see much in your question (or the original post) that was about "make project X work the same as Y in one click". That was not clear to me. Having been grumpy about the text, I then must go the other way - you are totally right about sharing config. I too would love to have a…
-
You will need to ask the Liquibase admins to remove you from it (or remove their application links in their application).
-
Oddly I spoke to an Atlassian about this a couple of weeks ago. She'd like to do it, but there's so little interest interest in it, it's unlikely to go anywhere. It appears to have no way to increase the customer base or widen the offering - the queries are in the tens, not the tens of thousands that Atlassian are…
-
You will need to install apps that provide macros like them.
-
I'm afraid there is nothing to retrieve - the error you see means that Confluence cannot write your page to the database, but that is where drafts are kept as well as the published content. It can't write the page into the database because of the invalid characters, so the draft cannot be saved.
-
That does not tell us what you are trying to achieve, you've just repeated you're trying to do something in a bad way.
-
Not in Jira you don't. Issues in a project have the same project key. HCLEXT and HCL issues are in different projects.
-
The first part of an issue key is the project key. So "project = hclext or project = hcl" will find the issues you have named here.
-
You say you have a plugin already, so I'm not sure what you are thinking you actually need here. Assuming that statement is wrong and you do want to create a plugin for lightscm as the second and third questions suggest, start at https://developer.atlassian.com/
-
You need to add the correct line for the ip address into the pg_hba.conf file. You say you have added it, but the error message is saying that you have not, so there must be something wrong with what you have added. Either it's looking at a different file, or the lines you have added are wrong.
-
This can be summarised as "make Jira do the job it was written for, in support of the organisation that employs them to do so" I think there's another question behind this though. Could you explain what you are really asking?
-
Not without doing your own code. Confluence has a bit of autocorrect built into it, but it's totally Atlassian centric and hard coded (I only really noticed it when Jira was finally rebranded from JIRA to Jira, but the Confluence code was still "correcting" it back to JIRA). It's built in at a low level, you'd be having to…
-
The main thing for this is that it is just the right size for a cup of tea - large enough to enjoy it, fine enough that the aroma wafts up, and small enough that you drink it all before it gets too cold. Oh, and cat. Because it's me.
-
* The server version of Confluence is available as a compressed installation, or as an installer for some operating systems. It's a totally independent application, with later versions of the distribution bundling almost all of its dependencies * Technically, there is no support. You only get support from Atlassian if you…
-
There isn't one. The result from a scripted field is not stored, like a lot of other stuff Jira shows you. Your question leads me on to something else though. Why are you asking this? Why are you looking at the Jira database? I ask that because SQL is the single worst possible way to get any information out of Jira, and…
-
I suspect that you've got more than one licence for the applications. With Jira there could be up to three licences involved, and all of them need to match. Could you go to Admin -> Manage applications and check what licences you have for all three applications?
-
Yes it did.
-
You won't be able to "get" unassigned issue types, there is nothing in the database for them. You'll have to infer it from the absence of data. This is one of many reasons that using SQL on a Jira database is by far the worst way to get any information out of it. Instead of messing around with a data structure that has no…
-
No problem, but please do not assume this is the "right" answer. It is, for a lot of people, but it does not fit every case universally. I think you already are doing what I want to recommend - go talk to the people who use your system. As a consultant, I could write/talk a ton of stuff about best practice with a lot of…
-
You will need to give us some more details. When you say "desktop application", do you mean ALM-works "Client for Jira" or something else? (The Client for Jira is the only Jira "desktop" I can think of) What logins did you create? And where? Inside Jira? Where are these logins? You then say you are unable to create a Jira…
-
Requests raised by email have to be mapped on to a request type. I usually set up a dedicated request type for incoming email, one which has no mandatory fields (then hide it from the UI users). I quite like the politeness of customising the "thanks, we've got your request" email with a line that says "we may need more…
-
We tend to keep them in the same project - it's the same team having to deal with the incoming requests, and it's best for a team to be working out of a single project.