Comments
-
Browse projects will only list the projects the user can see. If you want to hide a project, you need to remove the user's browse access to it. Check the permission scheme for the project and look at who has "browse". You need to make the user *not* match any of the rules in there.
-
Go to the project admin screen and look for the issue type screen scheme. Follow that down into the screen scheme, which lists the screens, and that's where you move fields around.
-
You've given this person the right to view the project. So he can see the project. I don't see any problem here.
-
Yes, it can do all of that, and a lot more. The caveats: 1. Gantt view - you'll need an add-on to do that 2. "Integration with Outlook" is meaningless, and you'll need to explain it before we can give you a "yes" or options. ("Integrate" is a suitcase word - while it's clearly got something in it you want to work with, we…
-
Atlassian don't do release dates publically, they ship when the team is ready. You can usually get a feel for when something will be released by watching the community and the JIRA project for the product
-
When you say "tickets are moved", do you mean they are moved from one project to another in one instance or between "JSD projects in cloud instance and.", whatever the . is supposed to be?
-
Advanced search should be simply Created > startOfDay()
-
JIRA builds a connection string from the parameters you enter, and adds some stuff to it that you don't need to tell it. I suspect that your password contains a character that needs escaping in that string, which breaks the string. Try changing the password to something without any special characters in it - P3nGu!n for…
-
Your project seems to require this "externalId" field, but your JSON does not contain data for it.
-
Go to the restrictions section on the page where you add them, and click on each restrictions "delete". There's no "no restrictions" function I'm afraid, you just have to delete each one.
-
The document you are trying to import from is not in a Word format that fits the specifications for that version. It's a known problem with MS Office - the internal formats are so inconsistent and non-standard, you often run into files that tell you that they're office and turn out not to be saved to the documented…
-
See https://confluence.atlassian.com/doc/server-hardware-requirements-guide-30736403.html This is out of date though - it does not account for the simultaneous editing, for which I would want to add another 2GB memory for a system with lots of users.
-
Duplicate of https://community.atlassian.com/t5/Confluence-questions/What-is-the-server-specification-when-1000-simultaneous-users/qaq-p/588866
-
Your question is not clear about what you are asking for, but I will try to guess what you mean. You want a read-only line of text in JIRA - if you really do mean a field with variable content, then you have two options. * A normal text field that you do not put on any edit screen * A read-only text field In both cases you…
-
Confluence doesn't have a function to disable notifications like JIRA does, so I'm afraid you're stuck for now. I believe there's an outstanding enhancement request for this though, so it might happen.
-
Ok, in JIRA speak, this is a "screen". Specifically, it's the "Create issue screen", which is configured on a project and issue type basis. A screen is simply a list of fields, in a particular order. You need to look at the project's "issue type screen scheme" and drill-down into that to work out what screen is in use for…
-
>Since this is my first post not sure if this the appropriate place for this question If it went "bang", Atlassian support is the starting point. When you're asking questions, or having ideas to discuss, or have problems that aren't critical, the community is usually better, as support is focussed on things breaking,…
-
What is an "issue template"? Do you mean the issue "view"? Or the create/edit/transition screens?
-
That is not a problem. Go to the workflow you are using and edit it. Add a transition that goes from the step before "waiting for approval" to the step after. Put a "condition" on it that says "only members of our 'skip approval' group can use this transition"
-
A label field lets a user enter whatever they want, although it will try to prompt them to re-use existing values. A multi-select field will collect the right data, and the list is controlled by the admins. Atlassian are moving towards making them look more like the labels/tags, but it's not going to happen soon.
-
I had to read this a couple of times, as "issue type" has a distinct structural meaning, and putting it in field names can be confusing. However, I do know what you've done. You have a couple of *fields* called "AdOps Issue Type" and "Yield Issue Type". Your query is only asking about these fields, so it's returning all…
-
1. See https://confluence.atlassian.com/jirakb/how-to-automate-backups-for-jira-cloud-applications-779160659.html 2. The backups are limited to 48 hours, so daily isn't going to happen
-
Have a look through https://confluence.atlassian.com/jiracoreserver073/searching-for-issues-861257157.html It's how to find issues and choose what data to report on.
-
No, there's no "undo" in JIRA. If you move the issue back, it'll take the next free number in the project, like any other issue move.
-
Have you got the workflow in "edit" mode? Could you give us a screenshot too - the behaviour you describe does not sound familiar.
-
My apolgies, I was too focussed on the SQL. Yes, absolutely do it with REST. I think of REST as a "UI for computers" - if a human clicks on "delete user from group" and something makes a REST call to "delete user from group", they both take much the same route through the code, and end up removing the user in the same safe…
-
The most simple approach is to create a new space for the non-IT folk, put your pages in that space and set the space access rights to "anonymous can see it". Before doing that, check none of your other spaces use anonymous access. Then you can point anybody who can see the server to that space and let them see everything…
-
Both. I can not recommend the use of SQL updates on a JIRA database, as they almost always cause problems because people don't understand the database. If you insist on using them, then you *must* have JIRA offline when you do it, and a proved backup, as it's not unknown for one tiny mistake to render chunks of the…
-
Yes, you need to stop JIRA, take a backup, run your SQL, restart JIRA and re-index it. This is one reason you don't do anything with SQL in Atlassian applications.
-
JIRA issues already are tasks in a task list (a project) If you need to break up issues, use subtasks, or have a look at the basic multi-checkbox field.