Comments
-
Only way I can think of doing this is with scripting or add-ons (Well, ok, database hackery, but I simply cannot recommend that. Ever)
-
Hmm. In this scenario, your use-case is broken. A user should be able to see what is blocking the progress. If they can't see it, it's useless information to them, and actually should not be blocking them because they can't tell what it is. In fact, it's the validator you have that is broken - that should be either limited…
-
Sam is right, a project is not "scrum" or "kanban", it's just a template guide for Software to create the first board for you (and choose fields, screens, workflows etc) Consider the case where you have a filter of "Project = ABC". You create a Scrum board from that filter. Then you create a Kanban using the same filter.…
-
The error here is thinking the "order by" clause has an effect in a quick filter. It can't override your board sort clause (that way lies madness, both in code and real life). So while it looks like valid JQL, JIRA has no choice but to ignore it. This is not at all clear in the documentation I'm afraid, and you're not the…
-
Partly. It is possible to have separate departments have totally separate projects, with no cross-department visibility (let alone being able to do other stuff). You can do that in any JIRA installation But, there's more detail in your points: >Jira should be installed as self-hosted version in a company Yes, that's fine.…
-
Ok, start with the version of JIRA Software - what is it? The resolution set flag is a relatively recent addition, and I notice your screen layout looks different to the later versions.
-
I have to echo the other two - there's no queue restrictions, an agent who can use the project sees all the queues. You can be a bit sneaky and use (automated) issue security to hide issues from users, and that will flow into the queues, with people not seeing issues inside queues that they're not supposed to see.
-
Crowd provides a user directory for each of the applications. You will need a Crowd administrator to tell Crowd that it should be a directory for the applications and that SSO is enabled for each one. Then, for each application, an admin for the application should configure the application to say "use that Crowd over there…
-
That's strange, it doesn't do it on my installation. There is code for it in "setup_user.sh", but it should only run once.
-
You'll need to find the atlassian-plugin.xml file in the source code, I think the file you will need to open up is jira-gadgets-plugin.<some number>.jar as that will contain that file.
-
You need to enable anonymous access to the issues so the non-JIRA user can see the data on the issue.
-
The project permission scheme doc is the most useful one here, although it is quite long and not a tutorial. You have got the right general idea on this, so I'll go over your points in order. You've created a new permission scheme - excellent Yes you would have to delete the defaults as they let everyone in Yes, you should…
-
Not quite. The idea of "admins create project" is right, but there are two ways to do it - you need to be either a JIRA administrator or a System administrator.
-
I'm afraid Vishnu's answer is the one you need. To cluster Atlassian products, you have to use Data Centre versions. You have no other supported option. (And even the unsupported options don't really work well enough to be usable in most cases) However, the way you have worded your question makes me think your customers in…
-
This is the same question as https://community.atlassian.com/t5/JIRA-questions/Can-we-create-a-cluster-of-jira-products-on-self-hosted-servers/qaq-p/583511
-
Sorry, I also forgot - Atlassian don't really have "reps". Feel free to ask the community detailed questions instead. We have a lot more real-world experience than Atlassian (there are about 2,000 Atlassians, most of whom don't use SD as an agent or admin daily. I suspect the community has way more than 2,000 SD admins,…
-
It's not "just a plugin", it's one of the first two "applications" for the JIRA platform. (You can argue that an application is a "jumped up plugin" and I wouldn't disagree to be honest, as it's only really the licencing that matters) Service Desk projects do have a simple link for SD Agents to say "create an issue in a…
-
No. You do not just amend a JIRA database. At the absolute minimum, you should have it offline, and have taken a backup and proved you can restore from it before you run any SQL. This is something you should do over REST.
-
It's a bit more complex than just "field configuration", as there's several bits to look at. The most simple way to achieve what you want is to get your screens and fields right for the first project in your list. Start with the "issue type screen scheme" for it, descending down into the screens and making sure you have…
-
And you need create permission in the target project. Also, you can "just change" the issue type, but only when the workflow and field configuration for source and target issue types are the same schemes.
-
Most of that sounds ok, with the exception of point 2. An Epic should not be a product section, it should be a (very large) story which has an eventual end. Moving on to your reported issues * I'm not sure why you need separate boards. Even if you do, I'm not really certain why it should be a problem, as I often tell…
-
I'm sorry, but the short answer is that you don't. There's two things in play here. First, the message you are getting is possibly a genuine warning, suggesting that your board might be estimating on one field, but not the time-tracking fields. (It might also mean you really haven't put data in, but I think you have)…
-
Create a custom field listing your teams. Leave the issue unassigned until someone in the team picks it up. Assigning issues to groups does not work. You open yourself up to "I thought someone else was looking at it" and in real life, that happens *every* time you allow it. It's fine to have a "responsible group", that…
-
No, the database tables in Atlassian applications are mostly not directly exposed, because they're really badly laid out for reporting. You should forget database tables and use the APIs that are exposed, they are far more easy to use and representative of what you really want to do with the information being held.
-
If you go on any JIRA courses, you'll find the experts all agreeing on "use roles". Groups are to be used in roles, global permissions, and very special cases. "Never use groups in a permission scheme" is a good start
-
This looks like your code is feeding a function a string that contains invalid data for a module key. Check the template key doesn't need to be encoded, and look at the url as well.
-
Service Desk shields the end users (customers) from the details of the workflow, and although the experience the customer sees is directly related to workflow, it's not configured in the same place. Have a look at the service desk settings to see how the customer-ui is mapped on to the workflow.
-
JIRA IDs cannot be duplicated, so I'm not sure what you are reporting here?
-
You are right about the Epic having to be in a project. All issues, of any type, have to be in a project. But, Epics are intended to be cross-project, and you can add stories from anywhere into an Epic. Your board doesn't even have to span the project that the Epic is in, you just need the Epic to contain one or more…
-
This sounds like you could use JIRA. If you set it up such that each "deal" you have is an issue, then you can do most of this straight away. On login, users go to a dashboard (although they can select other places to default to, a dashboard is still the answer). On the dashboard, you can add a simple "gadget" that…