Comments
-
The base url is a Confluence setting - it tells Confluence where you expect to reach it. The url is determined by your DNS services Confluence isnt pointing at your old url, it's your network that's doing it. You need to get the new url set up in your DNS system.
-
Hmm, well, that all sounds consistent to me, it's almost certainly something in the sessions going wrong. I'm afraid I'm out of my depth here - I've configured LDAP connectors, simply by following the docs to the letter, and I've always had it work as soon as I'd got all the parameters right, so I'm really not sure. I…
-
It sounds like your server and/or client are forgetting the session somehow. Could you tell us what authentication you are using? Jira off-the-shelf, Crowd, LDAP, something else? Also, have you tried a different browser? (I doubt it's the browser, but if they behave differently, it could tell us something). And do your…
-
Ah, good Yes, you can, although it's not quite a "lock". Behind the columns is a set of status, and moving from one column to another is effectively done by "transitions" in the workflow. You can easily edit the transitions, adding "conditions" to them which will stop people using them. In effect, blocking the move across…
-
Do you mean columns instead of swimlanes?
-
It's pretty much what the error says - the applications are being refused access to the database, it's not responding to the applications. Check the database logs to see if there's anything appearing to connect to it first, but I also notice * you're using a host name (Kraken) - is that resolving to the right machine? *…
-
You need "current reporter browse" permission to be enabled. It is disabled by default because it's complicated to explain and can break your system unless you fully understand how to use it (although that's easy to define - NEVER use it for anything other than "browse project" permission, and you'll be safe) See…
-
You need to go over your notification schemes VERY carefully if you've got two-way emailing going on. You need to make sure that the dummy users you are using for import and mailing have their "email me on my changes" flag set "off" and that the emails going out are appropriate.
-
Behind a Service Desk portal, there is a JIRA project. To enable "change type of issue", make sure the JIRA Project has the target issue type as well as the source type (check the "issue type" scheme)
-
You could try it in a test system, but it's a very large jump and I wouldn't recommend it myself - I've not managed a clean upgrade from anything below 3.10 to 4.2. I'd do what you suggest - 3.7 -> 3.13 and then 3.13 -> 4.2
-
You'd need to dig through the history to find out which admin did it (I'm including your admins and the Atlassian system admin in that group of admins). That needs to be looked at by Atlassian support, as it needs someone to look at logs etc. I'd raise it over at https://support.atlassian.com and specify the user and any…
-
Definitely need to see the logs for this one. Could you also show us the full definition of the scripted post-function you've got in that screen shot?
-
Ah. You had not mentioned Cloud. No. Cloud does not support LDAP directories. There is a beta programme for SAML integration, but the general answer remains "No LDAP on Cloud (for now)"
-
What about the rest of the steps? 3. Add an LDAP directory 4. Fill in connection details for it 5. Click test and then save
-
You can't do this. Project lead is a single user. You should, as Christian says, nominate many people in a new ROLE, but the project lead is, by definition, one person.
-
I am sorry, but this question is very unclear. Atlassian Cloud handles versions, changes of state and builds in a reasonably clear way, Specifically, you say "version number and build number with JIRA and track any state change using it, besides the version number". What does "besides the version number" mean? and "I've…
-
JIRA Suite Utilities is pre-installed on Cloud! You may need to activate it though.
-
Yes, you have created on-hold as a value for the resolution field.That has nothing to do with the status of issues.Most people would see "on hold" as part of a workflow, so yes, I would do it as a status in your workflows.It's not generally useful as a resolution because setting a resolution means "we've finished with this…
-
There is no "map" between resolution and status. Resolution is a field and Status is an indicator of where the issue is in the workflow. I suspect you mean you have created a status and put the wrong status category on it. If that is correct, go to Admin -> Issues -> Status, find "on hold" and edit it. You'll be able to…
-
Not really. Mandatory fields are configured by field configuration, which applies throughout the lifecycle. Most of us install plugins that provide "field must be filled in" *validator* functions for a transition and use them on the "close issue" transitions, but you are going to need to find and install one (or write…
-
Talk to Atlassian sales / support ( https://support.atlassian.com is the quickest route usually)- they'll help you swap the money from the JIRA Core server licence to pay towards your monthly Cloud subscription.
-
Our admins talk to each other before hitting re-index. The length of time is proportional to the number of issues you have in your database. If it's a few hundred, I wouldn't worry about the downtime. If it's tens of thousands, you'll cause significant downtime, so book it for out-of-hours
-
Re-indexing affects the whole system. It basically deletes the index and rebuilds it from scratch, from the data in the database. Best bet is to make all your changes and then re-index when they're all done, as running a one-off indexing operation is faster than doing it after every change. The message is also misleading…
-
The rank field is a "lexorank" trick, you are not expected to put it on a screen because it's not really human-readable. You are expected to sort or order by it and to adjust it by ranking issues higher or lower than others, but seeing it directly isn't helpful to humans. The data you're seeing on screen there (the…
-
You'll need to start with a definition of "being worked on". Is there something wrong with "in status X, Y, Z" and a simple dashboard gadget to show that broken down by assignee?
-
I think you need to tell us what you mean by "owner". If it's a custom field, then it should be working fine, so I suspect you mean something else. But you need to explain it.
-
Make sure the field is valid for the target issue type.
-
1. Don't - it shouldn't be needed in the overwhelming majority of cases. If you're doing it a lot, there's something suspect in your process2. Officially, reopen the issue, your workflow should clear a resolution when that happens because the implication is "something more needs doing"3. Add a transition from resolved to…
-
Your "edit" screen has the resolution on it. Remove it immediately, as it's damaging your issues. Resolution should never be put on a create or edit screen.
-
Yes, it needs to log in because it needs to read and delete incoming emails.