Comments
-
Ok, it's not been able to connect, so it has not created the dbconfig file. I sort of expected that, but had to check. The parameters you are entering look good to me, so I'm not sure what is wrong. Next thing to do is a look at the log file, which should tell us the full reason for the failure and contain the string it…
-
What conditions do you have on the transitions?
-
See https://confluence.atlassian.com/adminjiraserver071/migrating-from-jira-cloud-to-server-applications-802592270.html and https://confluence.atlassian.com/doc/migrate-from-confluence-cloud-to-server-298979321.html
-
1. You can generally adjust most of the tracking functions for a different weekend. 2 and 3. It's hard to say with such a basic spec. There is Portfolio which could help you a lot with this stuff, but it's well worth a look at all the addons in the marketplace that return when you search for "Gantt". Tempo might be what…
-
Sorry, that was not clear. An add-on is a chunk of compiled code you add to JIRA to add functions. A "full add-on" is an add-on dedicated to a specific purpose, rather than a collection of scripts for script-runner.
-
I'm not sure you could do it in ScriptRunner, it sounds like it might need to be a full-on add-on, as you'll need to create a storage system for the drafts.
-
Show/hide does not affect the screens like that. It completely hides the field from the issue type, so that it won't appear anywhere. That's why I say you're looking in the wrong place, and unlocking the fields won't help you - the fields are shown already, and you don't want them hidden. I get both of those fields on my…
-
This is not a "configure" thing. You will need to write code that can capture and store issue details somewhere, add some screens for users to find their "draft issues" and then re-fill a create-issue screen from the stored information when they use the option. I'd also recommend calling it "save draft", as many people…
-
You don't configure this in field configurations. The fields are not hidden and one of the reasons they are locked is to prevent people hiding them. You can add them to the *screen* you want to see them on.
-
See https://confluence.atlassian.com/adminjiraserver073/configuring-issue-level-security-861253265.html
-
This is a backlog view, it pulls the Epics out because you don't rank Epics. You'll have similar problems with the working board. But I can get you a view that might be helpful: * Create a filter for "issuetype = Epic" * Create a new Kanban board, selecting that filter as the starting point * Modify the columns to match…
-
It's in the project administration section.
-
The "hide transition" you're using only hides it on the JIRA view screen. It still exposes it to other methods that allow the transition. To stop the user using it, use a normal condition, not a "hide" function.
-
Your permission scheme is giving them full admin views, you'll need to amend the permission scheme or the user accounts to remove that access.
-
Check the permission scheme. There is a line in there that says "can assign issues", you need to adjust the permission scheme, or change the customer's roles/groups so that they do not match the permission rule any more.
-
If you are on server and the cog is missing, you don't have admin rights. If you are on Cloud, then you probably need to check with your site administrators, as they manage users.
-
Your workflow has a condition on the "approve" transition that is blocking him. You'll need to edit the workflow to find out what it is, and either change it, or adjust his account to meet the condition.
-
Add a customfield. See https://confluence.atlassian.com/adminjiraserver073/project-screens-schemes-and-fields-861253368.html
-
I think you've landed in the wrong place. You'll need to explain what this has to do with Atlassian products if you have not.
-
JIRA has "mail handlers" which process incoming mail. They do not currently have one that sets fields like that. There are some in the marketplace which can do this, and a lot more. The two that spring to mind are JEMH and JETI, but thre may be others. It's also possible to write your own.
-
They are part of your workflow. If you need a different workflow, then you can edit it and remove them. Otherwise, you actually need those buttons.
-
I don't know if there are any existing Cloud add-ons that do other pie charts. But you should be able to write one.
-
There is no "personal" licence for Confluence. You'll need to sign up to a 10 user Cloud licence or buy a 10 user Server licence (the server is a $10 annual cost!)
-
Yes, you can install it more than once, just make sure you give them totally separate installation and home directories, and of course separate databases. For Rapid upgrade, it's "go back to the backup"
-
A cascading select will do that, although it won't hide the list of colleges completely, just not offer the user an option. For a more flexible option 1. Create the fields separately and use something like the Behaviours module in the ScriptRunner to implement the screen-logic to link them together 2. Find and install (or…
-
That error means what it says. Your pririty list does not have "Critical" as an option. You will lose an estimate if the field does not exist for the issue type you are changing to. JIRA will warn you about data loss during the move. However, it won't tell you if you move to a type where the field exists, but is not shown.
-
You will probably need to find or write add-ons to do this. It's hard to say more than that without a definition of what you want from "dynamic fields", as it's a very vague term. It may be that JIRA has functions which already meet your needs.
-
Go to the space permissions and grant anonymous just view. Or am I missing something?
-
The first instinct I have is to suggest you check the project permissions and the users in the project roles. "Can't see issue" usually means they don't have "browse project" permission.
-
The option is there, as described above. But it won't help you with Scrum - JIRA Software ignores estimates on sub-tasks, so you'll end up with some very odd looking numbers.