Comments
-
Could you explain or show us where you are getting that server-id from? What does the "system information" page say the server-id is?
-
I don't see what use a watermark would be in the issue view, other than making it a bit less readable. But you could amend some css to do it if you must. On export, it's probably more css, but it depends - what export method are you looking at?
-
Ok, great that you've done that, it's an excellent test, but I'm sorry that all it does is rule out that being the problem. As you've ruled out the browse-users as well, I am stuck. I can only hope the support call finds it for us! I'd be really grateful if you could let us know if they can fix it and explain it!
-
The dashboard menu is generated from your list of favourite dashboards. If you look at the bottom of the menu, you should see "manage dashboards", go into that and you'll see a (searchable) list of all dashboards you can see. Some of them will have highlighted stars next to them. Search for "system" and add a star next to…
-
You asked about amending an application. With Atlassian stuff, that means a piece of software that you use and someone is running it for you to use. So if you want a change to it, you need to talk to the administrators of the application. I think you need to explain your question in a lot more detail. Starting with which…
-
See https://confluence.atlassian.com/support/atlassian-support-end-of-life-policy-201851003.html It will not stop working, just become totally unsupported.
-
In the script settings, is the output template set to be a number field? When you go to Custom fields -> Your scripted field -> Edit, what do you have set for a "searcher" for it?
-
I'm afraid there's no way to do this in Jira. There are some tricks you can play on Server with some apps, but Cloud only really has a couple of really clunky options for it. You can't stop someone who has "create issue" in a project from starting to create an issue of any type in the project. But you could * Use…
-
FWIW, Atlassian are probably heading in the opposite direction - SAFe names Jira Epics "Features", with Epics being higher up in the hierarchy. Because of Jira Align and that clash, it looks like Epics might be formally renamed to Features (although I suspect it will simply be optional)
-
Creating a new custom field does not populate data into that field for existing issues, it just tells the issues that they have a new field available. I am sorry to have to ask, but the previous conversations have confused me as to what the symptoms of this are. Can you tell me what happens when you edit an old issue? Is…
-
The no technical support actually means any support request could be answered with "upgrade it and try again". Atlassian don't usually do that, they'll still try to help you with links to docs or bug reports, fixes and advice on trying to find it. But they don't have to.
-
Global admin cog -> System -> Security -> Global Permissions Or cheat a bit - replace "yoursitename" in https://yoursitename.atlassian.net/secure/admin/GlobalPermissions!default.jspa On the user permissions, I'd like us to look directly at the permissions for the project (I don't need to see them, just have an…
-
Putting the cancelled status in the last column works fine for me. It represents the issue is "done", so when the sub-tasks are all in the column with their parent done issues, you can close the sprint. I'm curious to see why you still can't close the sprint - is it still the same error? Have you tried searching for the…
-
It means there are five unread notifications about this card. You can read more at https://help.trello.com/article/793-receiving-trello-notifications - there's even an animated gif there that shows a red bell appearing and disappearing as you read them!
-
Hmm. Two thoughts which might not seem intuitive (because they aren't) * Can you check your global permissions for the right to "browse users"? You don't need to go into admin to do this, you can check by trying to change the assignee on another issue, starting to type a name, or starting an @mention in a text or comment…
-
Ahh, I see, you're creating something that wants to talk to "Jira", without caring if it is Cloud, Server or Data Centre (not that you'd really care about Server/DC - they share the same code base). Technically, they're different products, and while the REST APIs for Cloud and Server are very similar, they're not quite the…
-
Yes, it will. You have modified some of the installation, and it is telling you about it so you know you have to think through re-applying the changes to the upgraded version. I'm not sure why you started to talk about migration. Edit - sorry, I should have said this sooner: The three files it is warning you about are not…
-
Your question stated upgrade, and the warning message you are getting comes when you are running an upgrade on an existing system. So I am now a bit lost on what you are doing.
-
Thanks Jack! I've told Atlassian they've got a load of broken links there.
-
Sorry, I should also have pointed to https://developer.atlassian.com/cloud/jira/platform/rest/v2/intro/ which is the stable Cloud version (version 3 is available, but in beta at the moment) If you expand the "issues" section on the left, you should see the "get create metadata" call documented.
-
Yes, the call is to "get all issues from a board". I'm not sure why you're trying to give it parameters which the docs do not say is there. The default is to return all the data for each issue, but have a look at the "fields" parameter for the call, that will probably help.
-
You don't really care what the Cloud version is. You can get to it if you really want, via a REST call, but it is of no use to you. It can change without warning, and it does, frequently. And it's a string of numbers, little more than a build number, not a Major.Minor.Point style version, so it wouldn't tell you anything…
-
Go to https://www.atlassian.com/software/jira/download and click "older versions" and look towards the bottom for a link to "archives"
-
You will need to amend your project permission schemes and possibly project membership. Ideally, have a permission scheme that names roles for "create issue" and "browse project" permission. Then make sure your group is in the roles in each project. Or you could name your group for those permissions instead (this is more…
-
Hmm, interesting, that doesn't happen on server - it changes the default selected if level is on-screen, and sets no level if it's not on screen. Thanks for pointing it out
-
Agile has nothing to say about logging time spent working on things. Most Agile practices need some measurement of estimates and how you're meeting them (or not), and you could use work logs as part of it, but mostly, they're not that useful. In Kanban for example, you don't care how much work is logged on an issue because…
-
See https://community.atlassian.com/t5/Jira-questions/How-prepare-Ubuntu-system-web-server-windowing-system/qaq-p/1481996
-
Nope, they can't use a default level if they're not in it.
-
Is that from the Tempo app, or another one that provides a start-tracking field/button?
-
Actually, they will be able to see the issue. Pretty obscure thing in the docs (I think there's only one line that mentions it), but to set a security level, you have to have to be part of it. So you can't create an issue that would be hidden from yourself.