Comments
-
I would still say issue security is the right way to do this. Define an issue security level to match each issue type, and then have a post-function on the "create issue" transition that sets it by issue type (have a different workflow per type)
-
You need to be an admin to edit the workflows. But the answer is as Alexey originally said - use workflow properties to shorten the list.
-
That looks like the definition of another board. Jira doesn't have any way to concatenante two columns together like that. The board in your first screen shot has a ToDo-InProgress column that isn't in this config I guess it might be possible if there's some App you've got that amends the boards like this, but I've not…
-
Your workflow is not setting a resolution. You will need to edit the workflow and For all transitions into a closed type status, add either * A screen that has the resolution on it * A post function that uses "update field resolution to <value>" For all transtions out of closed type status, add * A post function that uses…
-
This is explained in the link Gabrielle gave. You need to edit the workflow, find the transition and select it, then you get a box with "validator" as one of the tabs.
-
The epic linking needs to be done in Jira, Confluence is only capable of basic lookup and create.
-
Almost all the gadgets ask you to provide them with a filter (or project, which makes them use "project = xxx" as the filter). You need to create and save the filters you want to use and then you can select them when configuring your gadgets
-
It's under Admin -> System -> Audit log Hopefully, you're on a version that defaults it to "on", so it's been logging for you. You probably want to check the retention period as well.
-
I'm afraid Jira doesn't log the project creation date and time, unless you have the admin audit log enabled.
-
The object "issue" will only be available in certain places. Where is your script running?
-
You don't. It makes a mess of the conversation threads, so it's discouraged. You can edit them and delete the content, but that's just rude.
-
As I understand the terms, you're fine to do this. Atlassian understand the need for testing of upgrades.
-
It's quite likely that an inexperienced admin put the resolution field on the create or edit screen, so it got set on either of those actions.
-
Yes. Open Source licences don't get developer licences. You could re-use the licence on your test server though.
-
One of your users, or an automation are removing the data from the field. Check the history to see what is doing it.
-
The add-on that used to be available for SLAs that I've used is now part of Jira Service Desk, and the other one seems to have vanished from the marketplace. There are some others, but they're for Jira 7+, so you'd need to upgrade to use them (or just get Service Desk) There is no free version of Jira
-
Ok, try systemctl enable jira and systemctl enable confluence
-
That is what Carlos posted - you set the assignee to the component lead (and drop the field off the create screen if you don't want the users to override the "automatic" option)
-
It is available. Just not in the right order in the drop-down
-
You won't lose any data during an upgrade.
-
We can't. We don't know what system you are talking about. If you have landed on a Confluence system, then there will be a login option at the top right of the page (or in the left hand bar if it's "Cloud")
-
To tag users, you need to have the "browse users" global permission, granted by being a member of a group. I am guessing that by "fully paid licence", they mean "Jira users", and you're not a Jira user, but just a Service Desk "Customer", who doesn't get "browse users"
-
Not without add-ons. Best you can do without add-ons is write an external script that you run after project creation, to have it add issues over the REST API.
-
The url for what?
-
Ok, this site is the community site, for all users of Atlassian stuff to talk about it and hopefully help each other out. You can use your Atlassian account on support.atlassian.com as well, to get support from Atlassian.
-
Run the file as an admin, and answer the questions the installer asks you.
-
No, an admin needs to be able to see everything in order to do their job. For that level of separation, use two servers.
-
We can't tell you where your Confluence is, we don't know which one it is. When you have found out where it is, just go to the url, there's an option to log in on evey page when you're not logged in.
-
Your /etc/hosts and/or etc/hostname are incorrect and need fixing When starting Confluence, you need to run the start-confluence.sh explicitly unless it's in the path.
-
A broken network setup probably. Could you show us the full error?