Comments
-
Screens are the collections of fields for the internal Jira projects. You need to amend the fields on the portal definition, not the screens.
-
That's not really the right problem report. The email is being sent. It is being received as well. But the receiver is rejecting it because their server has been told to. There is nothing wrong with Confluence or your servers here, it is gmail implementing a rule that blocks it. You will need to either get gmail to accept…
-
You will need to buy a new Cloud service whatever you do. Atlassian will refund the server licences, if it's within the first 30 days after you got them. You must get in touch with them to do this though, as Craig says
-
Yes, you will need some code to implement a listener to do this. There are several automation add-ons that could help you do it - Automation for Jira and ScriptRunner for example.
-
They need to be agents then. Who you train not to use external comments.
-
You can't and there's two reasons First, some attachments are not directly readable. Imagine zip or pdf files - you need software to open and read them, SQL would not be able to find plain text in them. Second, attachments are not held in the database (unless you're on an old unsupported version of Confluence where you've…
-
There is one workflow distributed with Jira that cannot be edited. It uses the five default status that are off-the-shelf. Go to the list of workflows and find the "jira default" workflow (it may be inactive) You can rename the default status though, and all the applications provide project templates that can create…
-
There is no way to do it on Cloud, that I know of. It doesn't support the addition of the code you would need.
-
We can't help you with a statement like that. I could say "I want a kitten", and you would not be able to help me because you don't know why I have not gone and got one myself. You need to tell us what you are doing and maybe what the error is.
-
It might be. Sorry that this is a vague answer. You can install the whole Atlassian stack on one machine, and see it work perfectly. The main problem with that is not "doing too much", but "single point of failure" and "We need a machine with enough resources to run all the things" It is fine to run it all in one place. As…
-
Kewl, hope I have not ruined it for others!
-
My favourite riddle was more of a logic puzzle. I first saw it in Doctor Who (Pyramids of Mars - mid-70s), but I suspect most people know it better from Labyrinth in the 80's. There are two guards on your path. One will let you pass, the other will not (The choice is between Heaven and Hell in Labyrinth). You can ask one…
-
Am I right in thinking that I am using one to answer?
-
Possibly, but you need to define how you are measuring "progress"?
-
>Jira does not support this out of the box That is totally inaccurate. It supports "add one user, only allow access to one project". An accurate answer would be "The defaults you get out of the box need to be changed". Documentation links for that were given by Alexey.
-
Please don't mark incorrect answers as correct, it doesn't help anyone.
-
Wrong. I think what you mean is that it does support it out of the box. But you have to configure it away from the defaults, and understand the permissions properly in order to do so. I'm with you on the lack of warning that it's "open by default" and lack of Atlassian docs on the subject, and my opinion on the default…
-
You need to read the logs to see what it is doing.
-
Try the tick-mark next to the answers.
-
What do the logs say the error is?
-
For your SQL to work, you will need to have Jira off-line while it is run, and you'll need to re-index in full (a locking index) after restarting it. You're also missing stuff in your SQL which will cause you problems later, possibly some loss of data (although it won't be issue data) Please, stick with the API to do this…
-
Ah, I see, you're talking about an issue type. The pie chart has no way of knowing what your filter is selecting for, so it just reports on the issues it finds, no matter what you might be calling them
-
Not sure what you mean by "null status" in that list, but I would add - regular housekeeping, a good way to communicate with your users and manage changes (a Jira project is ideal) and monitoring with a proper monitoring system like Nagios or an ELK stack.
-
You will need to "translate" Jira into another "language". It will be a global change though, all "issues" will come out as "scripts", which is probably nonsense for most of your users.
-
Natively, the only option is "automatic assignee based on the first component selected", but there are plenty of Apps that would allow you to set up more complex rules that automate assignee. Of course, it won't assign to groups, as that never works in real life and is hence not implemented, but you could consider setting…
-
Can't open it. What are the errors thrown as the crash happens?
-
Labels are supposed to be created by users as needed. If you want a restricted list maintained by admins, use a multi-select field (and hide the label field from the project)
-
Where?
-
Yes, it is easy, but did you have a question?
-
Welcome! I like the "Future Atlassian Guru" statement. It reminds me of someone :-)