Comments
-
Ok, let's start with the most simple case - you have Jira Core. This has no boards that you need to think about. Every project has an "issue type screen scheme". This tells the project what "screen scheme" to use for each issue type. A "screen scheme" tells the issue what "screen" to use for three of the four primary…
-
Change the "recipients" to the main login group. I'd recommend not doing that though - a lot of your users will treat it as spam.
-
You will need to read the logs to see what it is doing. Start with <jira home>/log/atlassian-jira.log
-
I'm not fond of it, but the new one has a number of significant oversights and flaws that need fixing before I want to swap.
-
There's no way to do this. Admins get rights over everything.
-
Ahh, I didn't spot it last time I scanned it! The reporter of an issue needs to be a Jira user for them to get emails. As a portal only customer, they can't see the issue, so they won't be mailed about it. They should only get Service Desk emails.
-
The new UI is not going to server for quite a while. The off-hand remarks I've heard are around "possibly for the next US summit, but don't bet on it" (Spring 2019 before you ask) One reason is that it's not that great. There are a LOT of existing users who despise it, and really are not coming around to it. Atlassian are…
-
No. The assignee field is effectively a list of user objects. You need to give it the right user object for it to work. Your nFeed field needs to work from user login ids, not name.
-
It does. And the plain list of projects for the end user is what I would use to find uncategorised projects. I think Sanan is looking elsewhere though. In the admin section, the project list is all projects in alphabetic order, not grouped by category.
-
Be aware that some of the information is not stored. Either because it's simply not written to the database, or it done by business logic. The database can give you the permissions, and the raw user information including groups (but not a history of profile change). In most cases, you'll be able to do the basic stuff like…
-
Correct. I would not hold your breath - a request for starting search terms with wildcards has been outstanding in Jira since version 4.0
-
If you could configure Qliq to send an email, or run a script of some sort that can post data to the REST interface, both of those can create issues.
-
Not easily, it's part of the structure of Confluence, rather than configuration. You could translate it to a modified language, and some themes might let you rename it.
-
There's a bug on Cloud doing that at the moment, I don't know if it has made its way on to Server yet. Users who can't browse projects get to see them in the main list. It's rather an obvious bug, I don't know how Atlassian missed it.
-
No, spaces are a flat layer, there's no sub-spaces. There is an add-on called sub-spaces which makes it look like you can nest spaces, which might help you.
-
Issues is in the (really poorly designed) left nav, but you now have to go back out of your project to get there. Click on the Jira icon, then you should see a list with dashboards//projects//filters//things
-
Yes, you can have more than one Cloud instance. So, yes, have one instance with 50 users, and a second for 10 users with Tempo added to it (for 10 instead of 50!)
-
I think part of your response is missing. What type of user are they?
-
I'm afraid the ~ function does not work with wildcards as the first character.
-
That's the one I usually reach for...
-
You can't have a workflow scheme that only associates one type. It has to contain mappings for all issue types a project might contain (i.e. every issue type you have). So, your scheme always contains a default mapping, such that all issues that are not explicitly named in the scheme use that workflow. It sounds to me like…
-
See https://www.atlassian.com/company/events/summit-europe/about Pricing has not been announced yet, but I'd expect it to be similar to last year (not that I know what that was)
-
It's worth a look at Backbone and Exalate too.
-
Is the customer a full Jira user (they have a login that gets them into Jira so they can see the issue) or just a customer (they can only use the Service Desk portal)?
-
What macro is it? Or if it's an error before you get to adding one to the page, can you tell us exactly where the error happens? (e.g. you put { in and it crashes there, or you put { start typing the macro name and it crashes there, etc)
-
Jira, as risks naturally map on to issues, and it handles many types of custom fields. Most of us create issue types of "risk" and use them in their own risk projects for generalised risks and often within the projects for risks directly related to the project. There are some add-ons in the marketplace that are worth a…
-
Could you have a look at the application log next? <jira home>/logs/atlassian-jira.log usually contains some more information about what happens when a user fails to log in.
-
You are definitely not alone! That's why I wrote the plugin, and one of the things that got me into the community - you all helped me design and write it. But it still is for 3, and I'm not sure I even have the code any more!
-
Annoyingly, you still can't really do this. The project lead is exposed to users when they go to the project header, but that's it. Years ago (Jira 3.0), I wrote an add-on that provided a project panel that listed both sets of admins for a project (those with project admin, then the system admins separately). It is…
-
You've installed an application that talks to bitbucket. Without knowing what app you've installed, we can't answer your questions with any significant degree of accuracy, but at a guess: >what is it ? Bitbucket is a service for looking after git repositories >whats it doing ? No way to know unless you can tell us what the…