Comments
-
I will try to persuade Adaptavist I should visit the London one. Or keep kicking Neil Riley until he makes good on the threat to take me to Amsterdam.
-
There's nothing here to "restrict". If you move an issue to a new config that does not match the old config, you must migrate it to the new one. If you want to stop people moving issues though, just remove their "move issue" permission.
-
You can't change the base url without changing the url your service lives on. At present, you can't change the DNS that gives you that url for Cloud services, so, in turn, you can't change the base url. Your only option is to export your data to a backup, buy a new Cloud system with the new url you want, and then import…
-
You've structured the call as <part of query><field list><part of query>. Try putting the whole JQL part in one go, followed by the fields.
-
Jira Core still has integrations with Confluence, and they're pretty much the same as the one you get with Software. Service Desk is the unusual one, that's where Confluence additionally provides a knowledge base directly into JSD (as well as doing everything Core and Software do) If you move from Software to just Core,…
-
Security levels in Jira are based on what a user enters into the "Level" field when creating or editing the issue. There's no way you could base defaults on the security level because * Defaults for fields are done by context, which is determined by project and/or issue type, not other fields * Even if it were possible to…
-
Not much - I use a scripted field (ScriptRunner) which reads the current issue and echoes out the parent issue summary and/or key on all sub-tasks, and the parent (slightly annoying as it's duplicated data on the parent, but it lets you sort and export the data easily, so hey)
-
Kanban boards, by default, use "issue is in a released version" to remove "done" issues from the right-hand column. Have a look at the "sub filter" near the bottom of the main board configuration page.
-
A board is a view of a set of issues. You can share a board, but as it is just a view, it respects the security of the issues it selects for. You need to make sure the board filter is visible to the users you want to see the board (share that too) and also the issues in the project(s) the board is pulling them from (You'll…
-
Then ask them. Take this conversation to them. Point out that "where a group is used" is a very complex thing to try to extract from Jira (even before you install any add-ons). It is still possible, but it's going to take you a LOT longer to form SQL than it is to investigate every place where they might be used manually,…
-
I am obviously heavily biased here, because I work for Adaptavist. I have used both Zephyr and ATM in the past, and continue to use ATM with some clients. Mickey is completely right about the approach - it doesn't matter how much I were to tell you "ATM is the best", that would not really help you decide. You need to look…
-
It looks normal to me. What happens when you click the pencil icon?
-
I'm afraid that's a circular answer - "Why do you want to know where they are used?" is not answered by "I want to look at where they are used". Could you tell us why this matters and how it would be more useful than going into the configuration to check, understand and amend access?
-
Champions can move them to a "removed" area which hides them. Generally, we prefer questions to remain, so they can help people with similar problems.
-
Jira Software is an application that is installed on top of Jira Core. You can do three things here: * Get Core licences. The users with these will only be able to use Jira functions (you might as well uninstall Software) * Get Software licences. Users with these will have full access to Jira functions and be able to use…
-
Automate what?
-
That usually means that the proxy server cannot reach the services you have set up to be proxied. It's trying to ask Jira and Confluence for data, but simply cannot reach them on the proxy urls you have given it. Are the urls correct? Are they firewalled off from the proxy? Try a simple wget/curl/telnet to the services…
-
Ok, two things here >We tried with a post function and resolution is getting updated as ""done". But strike line is not appearing on issue key Correct. The strikethrough is only shown in places where it is not clear that the issue might be resolved. When an issue is in your "done" column, you should be able to assume it is…
-
Depends - what do you mean by "community edition"?
-
Change the system to a "private" install in general config
-
Probably not, but it depends, check the link Shannon gave, it'll take you to the list of supported platforms.
-
Warren's link is the second best option. Amongst * Built-in reports and dashboards * REST as Warren says, and becomes the best option when point 1 does not provide enough * Add-on reports dedicated to specific tasks * Add-on reporting solutions like EazyBI and Arsenale for the most flexible options * Writing your own…
-
1. It isn't. Jira_issues is not something jira does. 2. Look at the custom field Epic Link. However, a much better recommendation here - stop looking at the database. It's NOT intended for reporting, it's not suitable for it, and it's the worst possible way to look at Jira data.
-
Yes you did, you said "backlog" A backlog is a function of a board. The issues selected by a board are chosen by a board filter. So your backlog is defined by your filter.
-
OpenJDK is not suitable for running Jira. It does work for some versions, but it's not suported and doesn't work in most combinations. Swap to using the Oracle (Sun) version of Java and try again.
-
The main performance drag is the permission schemes. Workflow and issue types have a negligible effect compared with permissions. (You'll find the use of roles to be better than groups, and if you can use the "anyone" permission for any browse functions, that's the main way to speed them up)
-
If it's any of the usual errors, then there are warnings and errors in your log file. I can't tell you what the problem is unless you can find them. Without those, there are some wild guesses I can make: * Permissions, as Alexey says - you will need to check over all of them to ensure the right people have access * The…
-
Ah, so not the "jira issue view", but a board view. Those are different. They don't have all the options that issue view does. (The cynic in me wants to suggest it's because the developers don't want to handle having to work out if they need to refresh the board view on every change that might break the current view)
-
Customers are only supposed to see Requests, they do not get Jira user access to issues. If you want them to use incidents, problems and changes as different items to "service request", then you need to set up Incident, Problem and Change request types for them to use (which then map to Jira issue types for your Jira users)
-
Ok, and what is the board filter? And what are the "missing" issues types?