Comments
-
Cloud to Cloud project migrations are not easy and there's no way to do it in full with Apps. You have to download BOTH Cloud systems with the backup XML, create a temporary server system from the download of the target system, merge in the project(s) from the download of the system that has the one(s) to move, then…
-
You can't do either of those things as you describe, I'm afraid. The system dashboard is the default dashboard for all new users. You can customise it though, so if you make it generic and suitable as a starting point for all projects, it does become somewhat more useful. One thing I do is add a gadget that allows me to…
-
You can do this, but it is a little obscure. At the heart of this trick is "different workflows". Let us assume a very simple case - * You have one project where "Customer Requirement" type issues need to be protected * All the other issue types can be edited by anyone * The project is not sharing workflows or workflow…
-
You either deleted the user, or renamed them to "Former user" - the fix for it is to rename them back to what they were before, or not delete them in the first place.
-
Yes, as you deleted a user, Jira can't know what was there before. You will need to create new accounts to get the users back
-
For Cloud, see https://www.atlassian.com/software/jira/guides/getting-started/basics For Server, see https://confluence.atlassian.com/jiracoreserver/jira-core-server-8-1-documentation-938846148.html (but check the version selected at the top right) In both cases bear in mind the getting started docs I've linked to are not…
-
There is no way to easily replicate the way Trello works in Jira, but you can get close if you've got Jira Software. Create a Kanban project with the absolute minimum fields your users will find useful (You can take it down to nothing more than "summary" if you want, but it's probably better to allow Description as well).…
-
Start at https://confluence.atlassian.com/get-started-with-bitbucket/get-started-with-bitbucket-cloud-856845168.html - you probably need to run through the "working with repositories" part, after the admin of that repo has granted your access (if it needs it)
-
Cloud or server? Do you have Software installed?
-
What clears? Sprint is not clearing if you're changing sprints. Could you explain the problem in more detail please?
-
>My team of engineers ALL have admin permission Argh, no, you should never let this happen. This is why it's a mess. Anyway, on to the problem as presented. The "archive" permission scheme probably names the admin group as the one able to see the archived projects. The simple fix is to change that so that it is a specific…
-
The only way to do that is to have separate Jira installations. Your Project administrators can be limited, on a project by project basis, but Jira admins and Jira system admins (which you don't have on Cloud, only Atlassian have it) have access to everything they need to be Jira administrators, which is everything.
-
Well, it does, indirectly, because the property was to do with permissions to browse the issue, but it's a case that very few people run into.
-
Could you explain what this has to do with Atlassian applications? (and which one?)
-
There is no way to automatically import config like this into Cloud. You would have to download your Cloud instance, import it into a temporary Server instance, use Apps to merge in your configuration and data, then export the results and upload it into Cloud, overwriting what you have there already. The alternative to…
-
Updates. You don't need any connectivity (beyond the Jira server to the client (browser) you are using) to paste in a licence key.
-
This means the database process is unable to read its own files, either because of a permission problem or because the files are irretrievably damaged. You will need to restore the last known-good backup you took of the database.
-
Hi Rajesh. I am sorry, we can't work out what you mean here. You have put the entire problem into a single run-on sentence without any punctuation to indicate where it needs to be split up into pieces of description. I think you have two Jira Core instances, and that you are having problems with emails going out, but the…
-
First, I'd want to put it in "safe mode" - disable any Apps you've added and check that you have no attempts to inject any javascript in any field descriptions. Second, check if there are any modified files in "system information". There's always one file that has been edited (the jira application properties), but have any…
-
Change the notification scheme, removing the people to be notified of "comment edited"
-
If someone is no longer a user in your system, then you shouldn't be sending them emails anyway! This sounds like correct behaviour to me.
-
One quick question to potentially eliminate a known problem - are you using MySQL for the Jira database on the back-end?
-
I think you need to talk to the space administrators of the Web Experience QA space. We're end-users of Atlassian software here, not your admins! We have less access to, and less knowledge of, your Confluence than you do.
-
Not yet, but when there is, I would not expect it to change. Jira 8 has some significant changes in some of what it does, but nothing that particularly affects server sizing. You'll find some stuff is faster, but that's because of optimisations, mainly in the indexing, which means you could probably lower the requirements…
-
Welcome to the community! It's hard to say what you need to change, as we don't really know what you have done. Some code in a .java file and running atlas-run suggest you've done some of the basics you need, but we don't know what else is there. Did you have a run through…
-
Welcome to the community! This is an issue that puts too little information in front of you on-screen. We need to go read the log file for the actual errors. You can find this in <jira home>/logs/atlassian-jira.log
-
No. 8 does not do this and Atlassian have said they're never going to implement anything like it.
-
Welcome to the community You can create different "field configuration schemes" which allow you to set the show/hide flag differently. See https://confluence.atlassian.com/adminjiraserver/specifying-field-behavior-938847255.html
-
It remains the best answer. I don't believe there is a better way to do it until the whole workflow and events system is redesigned.
-
Welcome to the community! It is mostly harmless to create loads of issue types, technically. There is some overhead, but it's utterly trivial compared with other factors. The human down-side of many types far outweigh any technical considerations. Specifically: * Your admins will struggle with vast lists of similar types.…