Comments
-
It's simple view tracking as pages are requested, stored alongside the pages. The tracking add-on has to be enabled for it to gather the data.
-
That's because it doesn't do anything more that is not documented on that page! What else are you looking for?
-
No, they'll always see the status available. But you can effectively make totally different paths through the workflow for different teams by using "conditions" like "only team A can move to status "blue" and only team B can move to "red"".
-
You would find it better to remove the "application user can see everything", but there is a slightly higher maintenance way to do what you want. Create a new group for "guests". Give that group access to *only* the project(s) they should have. Add that group into the "can use application" global permission, but not the…
-
Admin again, then look for "workflow schemes" this time. Have a look at the project, find the workflow scheme the project is using, make a copy of that, then go into the copy, and change the old workflow for the new one you've just made. Then go back to the project admin and change the workflow scheme to the new one. You…
-
Check the issue type scheme for the project - I suspect that only has 10 issue types.
-
Go to Admin -> Workflows and find the workflow you want to amend. To the right, you'll have a "copy" link. Yes, your guess about the goal is spot on.
-
Site-admins are able to maintain the Cloud site - mostly users, which are shared across the applications that make up the sie. Jira administrators look after Jira - fields, screens, workflows, projects, permissions and so-on. Confluence administrators look after Confluence at a similar level. You can change the permissions…
-
Download a copy. You only need it temporarily.
-
You need to take the 7.3 export, import it into a temporary dev/test system on 7.3, then upgrade that system to 7.5 and export it. Your production 7.5 will then be able to read the file.
-
Not a clue, you haven't explained what any of that is in relation to Atlassian software.
-
There wasn't a problem there, just people not quite understanding the access model for Service Desk, and the changes being made.
-
AS discussed at https://community.atlassian.com/t5/Jira-Core-questions/Issues-created-after-upgrade-still-displaying-after-manual/qaq-p/648708 , I think you have broken your system with a partial roll-back.
-
The roll-back process you've described here is broken. If you didn't revert the application directory back to one that matches the restored data, it will have tried to re-upgrade the data to the current version, but with a home directory that contains data from the previous version. I suspect you need to go back to the…
-
It's the same - Only issues that are in the far right-hand column of your working board will be seen as "done"
-
What "problems"? You'll need to be specific about what you've been reading. I don't see anything in your description that Jira Service Desk does not handle ok, although you will need to write code to connect your "web forms" to Service Desk.
-
Put the cancelled status in the last column on the board.
-
Duplicate of https://community.atlassian.com/t5/Jira-questions/Condition-Validator-for-creating-unique-issue/qaq-p/648636 which has an answer.
-
"Permission denied" means your account does not have the right to run it. You need to talk to your server administrators about granting that permission to it,
-
This is quite a well-known error. Jira talks to itself as though it's a user. You need to make sure that the Jira server can resolve its own address on the base url you have set for it. Log into the server, an on the command line, try "curl https://shield-solutions.com" - does that work, and give you some login text for…
-
Nope. Can't do it. There is no direct relationship in SQL. You need to read the form to work out what is on it, then parse the queries building it to work out what issues are there.
-
If you are the only user, then you are the system administrator, as the system is initialised using the first account you create. But you should see that in your groups.
-
Did you take Jira offline before making the change? And Re-indexed in full afterwards?
-
Try https://www.linkedin.com/pulse/how-study-jira-administrator-certification-rachel-wright/ - it's a really good write up of how Rachel got there.
-
No, we need to see the logs to see what is happening when the post-function runs. Why don't you have access to the logs? Can you ask?
-
One of the (dis)advantages of Cloud is that it keeps things simple. You have no access to the database on Cloud, or the internal API. If you want your data warehouse to pull data from Cloud, it will have to do all the work over the (incomplete) REST interface.
-
This is a bit difficult. In Confluence, you can easily use the Jira macros to pull data (especially status) from the Jira issues, but these don't update a Confluence page, they just report on the issues. I think your question is a bit deeper than that, but I don't want to project my guesses or instincts. Could you go into…
-
Sort of. Let's say "too long" is a day. Run a filter for something like "updated < -1d and resolution = unresolved". The will give you a list of anything that's open and not updated in the last day, so it's probably going to be quite a long list, but I'm aiming to give you a rough idea, not an absolute. It's a query you…
-
Don't. SQL is the single worst way to try to report on Jira data. Please, form a query and do it via the Jira UI or REST calls. What report are you trying to generate here?
-
You can link between them, but the two systems are, well, two separate systems. The closest you can get is to use the same SAML based user directory to provide the users to both systems, but deep down, both systems will be treating the users as effectively copies of each other. Your best bet is not tight integration here,…