Comments
-
Could you explain which Atlassian application this applies to and exactly what the trigger is ("user has come back" doesn't tell us much)
-
What Testing add-on are you using? If it's not a testing add-on and you are looking at JIRA numbers, then the most likely explanation is that someone added and then moved or deleted 197.
-
Ok, this is yet another duplicate of https://answers.atlassian.com/questions/117052/what-is-the-problem-with-this-code-in-jira-4-4-5-for-select-list-why-the-list-is-always-returning-null-value where more information has been posted
-
Have you tried looking at what the strings actually are? Insert a debug line at 9 to look at what fieldValue and status actually contain? Ahh, hang on - what is "getDefaultStatuses"? That looks like an internal function you've written. You'll need to debug that to work out why it's returning a null.
-
That's why I said the docs are misleading - they don't say that, but it is right. The admins can't see the content of the restricted page (unless they are included in the restriction). But they can see that the page is there, and change the restrictions.
-
True, although the system admin has all the same permission and restrictions related rights. The system admin stuff is about looking after the server side (Which Cloud admins don't need) And, of course, both types of admin can see and change page restrictions, irrespective of space permissions, because that's an admin…
-
No, the point of the administrator's job is to administrate the system. If they're restricted from getting to parts of the system, they can't do that job. If an a person leaves, that's exactly the case where you need your system admins to have admin rights - they can find and change the restrictions left behind. This is…
-
The doc is misleading. Not quite "wrong", but the section you've quoted is misleading. A user with admin rights has, well, admin rights. Not the ability to see and do anything. They can grant themselves the ability to see and do anything, but the admin right does not grant them any "browse" rights automatically. They still…
-
Yes, order by can be done and saved with filters. Some reports on results honour it where it's relevant.
-
Yes, but it's not quite "by page". You have to make the space in which the page lives accessible to "anonymous" users. This means they will be able to see the whole space. When we do this sort of thing, we tend to either * have a simple rule that we know which space (or spaces) are totally public, and educate our writers…
-
Hmm. That's a little unusual for Atlassian, there's no quick reference or link to it on the overview. Anyway. Try https://bitbucket.org/plans
-
Have a look at https://confluence.atlassian.com/jira/jira-requirements-185729596.html
-
You have a choice between: * You already have upgraded it, you need to run 7.2.4 against that database * Several months work trying to unpick a database in order to downgrade * Revert to the backups you took before the upgrade
-
Bear in mind that if you just flip the version number and run an older version of JIRA, you're likely to find that it either * won't start, throwing a LOT of errors * will start, but display damaged/destroyed/unusable data * will start, but actively damage or destroy your data When you have a 7.2.4 database, you must run…
-
Ah, the workflow changes might be an issue, yes. Checking on the next sprint end is the best plan!
-
Are all of the resolved issues in the "done" column?
-
You just need a resolution set (any resolution), and the four status you've mentioned in the done column
-
It sounds like they are not being "closed" properly. I'd check that a resolution is being set correctly, and then put done, closed, ready for release and released into the "done" column on the board.
-
Do they have the project permission to "add and maintain watchers"?
-
Shouldn't actually matter that much - the base url is important, but getting it wrong does not stop Confluence being accessible. You can still use the admin functions, including "change base url" by connecting to it on the actual url it is running on.
-
You'll need to explain that a lot more to get a useful answer.
-
The problem is exactly what it says it is. You have a user directory which you do not have access to write to. JIRA admin grants you JIRA admin, it doesn't grant you rights to edit the content of external directories unless you explicitly set it to. Go to admin -> user directories, I suspect you'll find at least one is…
-
Right, well, that was easy. You're installing a version that is not compatible with your version of Confluence. Try installing one that is compatible - see https://marketplace.atlassian.com/plugins/com.atlassian.confluence.extra.team-calendars/versions
-
Still no logs I'm afraid. The error message really does mean we need to look at the logs.
-
There is no screenshot or logs. Could you read the log file to see if there are any hints in there?
-
That's a problem with no real answer. Assuming you are using the full range of possible configurations within Jira, then there is no way for Jira to tell a user anything other than "automatic", because there is no way it can establish the assignee until after the user has filled in the fields and commited the creation of…
-
"Get" in what sense? Plugin code? External system? Do you really mean issue status or the actual column name?
-
That looks right to me, you do not need to mess with databases or anything like that. DNS and the base url via the admin GUI are enough. Except... if you have used application links, you'll want to update those as well (again via the gui). And any other applications that are pointed to JIRA or Confluence.
-
Ok, could you also check what happens when other users get similar emails? (Sorry, that sounds obvious, but I want to be sure that the problem is in his settings somewhere and not with what Confluence is sending. What we're looking for is the difference between a working email and a non-working one, and a comparison might…
-
They've not got access to JIRA, so outlook can't fetch everything referred to in the email. May need whitelisting in the outlook settngs