Comments
-
I'm afraid delete means delete, you have to restore from a backup (everything, which will destroy any data entered after the backup was taken. And that assumes you took one at the right time)
-
No, they'll need to "watch" the page. Watching is very different from "being able to see". I'm not sure why anyone would want to automatically watch pages just because someone else can't see them.
-
Start with a look at the space permissions - they need to show "anonymous" access for any page in them to be public. If you don't have anonymous there, the page is private, limited to those who have "use space". If you do have anonymous, then look at the restrictions on the page - if there are any, then they should say…
-
This means you have pointed a second Confluence installation at your database, and started it. You need to decide which one of the installations should be active and only start that one.
-
I know what you're trying to do. You need to use the Assignee from the issue, not a custom field that does not exist.
-
I can't help you past "you need to ask your administrators". We can't know who they are, it's not our system.
-
Yes, only grant them schedule and edit. Do not grant them "transition"
-
This behaviour means one of three things (but annoyingly will not tell you which one) * Your password is wrong * Your Captcha entry is wrong * The system can't connect to the user directory to confirm your credentials You will need to read the application log to find out which one it is.
-
If you want to be an admin of a system, you either need to be the person who installs it and hence able to set up the admin, or you need to ask the current administrators to give you admin rights.
-
Exactly where I was headed, thanks @Robert Barrow
-
Ok, so you need to use the Assignee field, not the non-existent "assignee" custom field.
-
When you say "moved around", do you mean "move issues" (between issue types and/or projects), or do you mean transitions through the workflow? Or something else?
-
Yes, see https://developer.atlassian.com/server/jira/platform/rest-apis/
-
The error log tells you that on line 9, there is an error with getCustomFieldValue - the most likely reason is that you have fed it nonsense for the custom field, so I'd then look at line 7 where you set the variable. Best guess - you don't have a custom field called "assignee", or you have two or more.
-
What are you doing, what is the user system, and what are the error messages or symptoms?
-
That is a link to the "home page". Change the home page as I've described, setting it to the space page you want it to land on.
-
True, this will work. A direct copy should be ok. But workflows are often not the same even if they look the same, and more importantly, often drift - you can only be 100% sure that they are compatible if you know you are the admin who copied it and the only one who might edit it (and won't because you know of this issue),…
-
The "home page" for Confluence is either the dashboard (by default), or you can set it to a specific space's home page in admin -> further config (I think it's in there, it may have moved in Cloud)
-
You can logically entangle them, accidentally. The most obvious way to do this is to have a workflow validator that checks a value is filled in a field. If your new screen scheme does not include that field, the user can't enter it and hence can't progress through the workflow. But that's probably not going to happen often.
-
Actually, not quite - the .getCustomFieldValue will return a Project object directly (at least my slightly old code didn't need to cast it). try issue.getCustomFieldValue(cf).getName() directly - my code is old, but I don't think it's changed!
-
2019 and most don't need or want it. Atlassian dropped it from the to-do list years ago, due to lack of interest!
-
Jira Service Desk and Jira Core (Service Desk is an application that runs on top of Core, so you need the Core install to support it)
-
Oh, hang on, you said "multi-select" field and I went with it. But it looks like it is not a multi-select, but actually a project field! Could you confirm the exact custom field type in the list of custom fields under administration -> issues -> customfields ?
-
Issue type is not really a simple "field". It's a structural property of an issue, off which hangs a load of configuration data. My guess is that you have different workflows for Incident and Task - these hang off the issue type. So if you just change the issue type without doing all the workflow migration, they will fail,…
-
I think your message crossed with Tarun's? His import line is what I would have typed.
-
Ah, ok. You have a problem then - the standard way to tell Jira a field cannot be edited in "view" is to remove it from the edit screen. The "inline edit" is a friendly way of making Jira quicker and easier for your users - changing a field becomes three clicks instead of 6. If you want to disable inline edit while keeping…
-
You should never change the base url in the database - please undo that change and re-do it properly, using the UI to update it. To fix the main problem that you can't reach the site though, you need to give it the url (or IP address) that Jira is running on. If the base url is wrong in the application, you will be told…
-
Um, your question says "make text field read-only in edit screen" then "the user can change this field in edit screen" - which one is it? Or do you mean you just want to be able to stop all edits of the field after creation? (To do that, remove it from the edit screen)
-
Ok, that's good. Now drop the 8080 for the "outside" of the proxy, as you don't need it, just go to http://IP as that's what your proxy will be set to serve. (I'm assuming the s$ on the end is a miskey)
-
Argh, really sorry, I linked to Confluence instead of Jira. See https://confluence.atlassian.com/enterprise/jira-sizing-guide-461504623.html instead, alongside https://confluence.atlassian.com/adminjiraserver/jira-applications-installation-requirements-938846826.html