Comments
-
Oddly, this would be the same answer as was given the last time you asked a nearly identical question. https://answers.atlassian.com/questions/65661/about-the-licences
-
In theory, sort of. In real life, no. If you want to do it, you have to make sure that every library that they share is on identical versions, and that's not happened since about version 3 of JIRA. Don't do it, you will hurt yourself.
-
You can't - the whole point of that drop-down is to allow you to see all the possible assignees. I'm not sure of the exact logic of the suggestions, but to change it, you'll need to hack the code providing it. (Which you can't do with OnDemand installations) The best you can do is take another look at the permission for…
-
Ok, the localhost being functional means that JIRA and Confluence are running, so this is purely down to the proxy. Getting a directory or 503 instead of the application means that the proxy is simply not looking for JIRA or Confluence. As the first document you've mentioned works fine for me, the question has to become…
-
I think there's a missing question here, but I suspect the question is either 1) Does JQL have a "group by" clause? To which the answer is "no", because JQL is for finding issues, not displaying the results of the search 2) For internal users, the SQL for groups is simply "have a look at the membership_base table"
-
Right, now you need to make sure that the field a) exists for bugs - check the field context in the list of custom fields b) is shown for bugs in that project - check the field configuration
-
Ok, now try "project = OurProject and issuetype = X" (where X is a single issue type and the query will return at least one issue)
-
I'm sorry, that does not tell us anything. Could you post the JQL you are using?
-
Could you tell us what the JQL is for the issue navigator? It sounds like your JQL is selecting issues based on the fields you have hidden, so it makes sense that they'd be dropped. As an example, if you have a field "colour", your JQL says "colour = red" and then you hide the "colour" field in project X then JQL will be…
-
The backup is xml, so I'm not sure what you're reading. Granted, it's laid out in a way that is better suited for system transfer than for issue reading, but it's still xml, and it's still everything.It's also your only option on Cloud (other than doing many queries)Your best option here is probably to think about your…
-
Eh? Run a search and click on the "xml" option if you want a sub-set of the data, but as you say you want everything, I think the "export" option at https://confluence.atlassian.com/display/Cloud/Import+and+export+data will give you everything.
-
Ok, great, that explains most of it. My question now is what the issues and versions have to do with your storage process? As a side thought, why aren't your build/release team putting the binaries directly into Nexus?
-
Ok, that's vague and doesn't tell us much more than you had before, but it's getting there. Some more questions * What are these binaries? Not their content or type really, but can we assume a binary is just "a file I have"? * Where are they coming from? * Where are you wanting to store them? * How do you want to use JIRA…
-
Could you please give me the context of what you are trying to do. I cannot make head nor tail of your explanations without that context. I don't care that it's an automation, I need to understand why you want to do this so I can understand what you are trying to get out of it.
-
So imagine the "end user" is your automatic process - what should it be getting from JIRA and why?
-
I'm sorry, that still does not explain it. Maybe if I knew what you were trying to achieve, I could get more from your explanations - some context often helps. What are you trying to give to the end user? Not how, but what should they see and why?
-
How are you storing that? How do you know which one is released? An issue can have several versions which might be unreleased, released or even archived.
-
Probably not, as the result is a list of version objects. You haven't said what details you actually want.
-
issue.getVersions() is a start. I don't know what details you need from it.
-
Nearly, although I think you really mean what I am about to say. You need to give the script parameters when you call it, and then you can use the data passed into it in the script.
-
I'm not sure I can explain it. Modify the code Stefan gave you adding the parameters, then modify your shell script to do something with them.
-
>Why i am do this means I have store the all the binaries at one place by using the versions, this is the way easy to deploy the binaries per a required version numbers That's a terrible way to "store the binaries", if I understand what that means. In fact, you don't need to do it at all, as all the information is in JIRA.…
-
Please, could you explain why you want to do this? Also, you say you don't have any scripts, but the question was "how do I run a script". Which is it?
-
I don't know what that means. You're trying to write data to a file with a script (probably a very poor way to achieve your goals). If you don't tell the script what you want to write, it can't write it.
-
If you pass the data you want to write to the shell script as a parameter, you can do whatever you want with it. However, my "fix the actual problem" instincts are screaming here. "I want to write data to a file" is a solution to some problem, but it feels like it's probably a very poor solution. Could you tell us what…
-
Erm, then you didn't use the Software installer. If you got a success from the Software installer, then Software is installed. Anyway, however it's gone missing, you can still add it back, even when you can't connect to the marketplace directly. See…
-
If you used the JIRA Software installer to install JIRA, then JIRA Software is installed. So you must be removing it somehow.
-
Ok, so how did you remove it?
-
No, I think you've got a bit confused (you're not the first) Under JIRA 6 and below, you had JIRA with add-ons. One add-on was "Agile". Under JIRA 7, the Agile add-on goes away and is replaced by JIRA Software. You can install (and upgrade to) JIRA Software in two ways - install JIRA Core and then add the Software…
-
Ah, I posted before you'd written a question - there was only a subject before. However, if you're running that .exe file, then you must have deliberately removed the application from your installation. To put it back, have a look at…