Comments
-
No harm in asking if you can't find something!
-
Components don't work that way, they are a flat layer. There is no nesting.
-
Go to project admin and work your way down through the "issue type screen scheme"
-
Ah, sorry, I saw proxy in the source system and assumed you needed the same. It doesn't change the answer though. Your DNS entry needs to point to the public address of your server, and you should set the base url to that address in admin -> general configuration.
-
The same way you get them on the issue edit screen - go to the screen that is in use for "view" and add them.
-
You should check the dates on the documentation you are reading. The remote API switch went away around Jira 6.4, as that introduced internal functions that rely on it. Obviously Cloud is way past that version. There is no switch, the REST API is always on.
-
You would need to create the Bug in their system. Either do it manually, or have a look at creating it with a REST call from one of your systems.
-
Not natively, but you can add one as a custom field. It won't have any of the functions of the actual status though, or be a workflow.
-
Ok, you should work through https://confluence.atlassian.com/jirakb/hmm-we-couldn-t-create-your-project-due-to-an-unknown-error-818580338.html
-
Well, you were reading a conversation ranging from 1-5 years ago.
-
I am not sure what you mean by "just plain ip address on port 80 and a corresponding DNS record". You only need one thing in there - the single url your users will be using Jira with. Could you explain exactly what you have in there?
-
Postgres is probably the most widely used, because of the combination of cost and that Atlassian develop for it first, and use it for Cloud. I tend to recommend Postgres second, for those reasons, then often MySQL third, Oracle fourth, and MS-SQL last. I've had poor experiences with all four of them, but MS-SQL has by far…
-
Add-ons like Script Runner and Automation are your only possible "fixes".
-
You can't change the directory in more recent versions of Confluence (think it changed around 5.5). But, yes, this is a standard thing to do - I usually stop Confluence, copy the existing attachments tree to the share, (re)move the attachments directory and then create a symbolic link to replace it. Pointed at the share,…
-
Scared me there for a second! It's not the new Cloud layout, which doesn't work properly yet. Just the colours, typography etc.
-
Message fields look like custom fields to Jira, so give the "where's my field?" function a go to start with. You need them on screens and not hidden by field config, like other custom fields. However, there are some quirks with them 1. View really mean view. Despite the fields always being read only, Jira has two modes for…
-
Also, for some custom fields, you will probably need to join on the "options" tables - specifically, select type fields. I can't recommend Micky's first line more - please, do not use the Jira database for anything, it's a nightmare for reporting. Use the REST API.
-
What is an "epos"?
-
You can, but it might be quite complex. You would need a field that could read the other Jira over REST and grab the list of projects. There's a couple of approaches to this - you could write an add-on to do that as a field, or use an ordinary custom field and have a script that runs regularly, updating the option list…
-
I know of at least three, although they are mostly involved with us for more Confluence reasons than Jira/Service Desk. I can't name them without asking them, obviously, but I'll ask my contacts to comment here if they can.
-
Even reading can be a risk, and inaccurate when data is being cached. You'll need to compare your my.cnf files to start with.
-
You can do this, you've always been able to do it in Jira. Look for the "create sub-task" link on the issue, after checking the project has an issue type of "bug" as a sub-task issue type. The problem here is that you can't create sub-tasks in Zephyr.
-
It's blocked, to force you to report bugs the way they now need you to - via a Service Desk. Please follow the links to "report a new bug" in your screenshot, although the description you've given sounds more like you need to raise a support request.
-
Ideally, stop reading the database with SQL, as it's the worst possible way to report on Jira data. Then you don't care about quotes. Your test and production servers have been configured slightly differently, and my guess is the production server has been set up to be case sensitive or with a different character set than…
-
Did you take your Jira completely offline before making the changes, and back it up in full? What do you mean by "mapped"?
-
The "out of the box solution" is to allow you to modify the workflows to fit your process. Adding a new status to a workflow is not that hard, or scary, and even if you do get it wrong, it's easy to fix as well. We don't see many published workflows in the marketplace or community because generalised ones are almost always…
-
Absolutely. It does sound like you need "disallow edit after it moves off a board". So, if your "not on the board any more" depends on status, you're good to go, because you can just stick the "do not edit" flag on status that are not on the board. If your boards are not selecting by status, then you're a bit stuck though.
-
But that will stop all edits to the issue, not just that one field. Also, it won't stop "edits" to status. Status is not a field, it's an indicator of the position in the workflow. To change it, you use transitions that move the issue to a new status. The edit property does not affect status changes. To do that, you need…
-
No, he's not paid. We're a community of end-users trying to help each other out. Atlassian are here and they do pick up questions. You'll see their profiles are highlighted with "Atlassian", much the same way Tarun and I have "community champion" For this question, the answers are there, but they are scattered through the…
-
Yes, the next step is to start reading logs. To get something clean, I'd stop Confluence, then go to <confluence home>/logs and move, rename or delete all the logs in there, then restart it. You'll at least get a clean set of logs to work through!