Comments
-
I'd think about the audience rather than the groups. Who is going to be reading this documentation? How is the end user likely to be understanding it? As an example, let's say you've got a load of Financial traders who use trading applications. They're not going to care, or even know what group owns what application. When…
-
Well, actually, the code you use is irrelevant. Whatever language you use, you'll want to talk to JIRA over the REST API Start with a look at https://developer.atlassian.com/jiradev/jira-apis/jira-rest-apis/jira-rest-api-tutorials/jira-rest-api-version-2-tutorial . This has some pointers to some code, and I'd recommend…
-
No, there's nothing wrong with your query. The query is looking for issues that were created "before (now - 4 hours)", or in English "more than 4 hours ago". That means *Everything* over 4 hours old. I think the problem is that your question is not right. When you say "Need a JQL to list all the tickets that have been…
-
The usual way to do this is to use a proxy web server on your site. These let you do things like www.somewhere.com -> Main website www.somewhere.com/jira -> Jira www.somewhere.com/thingy -> thingy application www.somewhere.com/holiday -> holiday application
-
Your > is the wrong way around, it's saying "created in the last four hours". I think you want "updated < -4h" - that will give you all unassigned issues that have not been updated (including created) recently.
-
Right, that's a totally different thing. Cloud doesn't have much in the way of an import facility for single projects. The best you'll be able to do is export a list of issues to CSV and import it into the project as a simple list If you want to do the whole lot though, there's methods for moving from Server to Cloud…
-
As far as I can remember, you either have to turn off the module that provides it in the system plugins, or implement a user directory that it can't control. Are you using the internal directory, or something else?
-
Why? You'll be duplicating issues into separate areas. Who do they belong to now? Do you really have two streams of work for each set? Why don't you just change the project type to Service Desk?
-
Yeah, that document is wrong Try Admin -> System -> Password Policy However, as it doesn't pop up in the search, it may be disabled in your system.
-
Where? What system(s) are you thinking of? You should not even think about doing it with SQL, it's not going to be pleasant.
-
It's the operater precedence, your "or" is not joining the clauses in the way you think. What your query actually says is (Project, sprint 4, bug), or tasks, and completed Try explicitly boxing the "or" out: project = "name of the project" AND Sprint = 4 AND (type = Bug OR type = Task) AND status != Completed
-
I don't know how you're doing the hipchat integration, so I don't know if it will keep repeating the notification. The query snippet I gave you will continue to report the issue whenever the query is run, so I suspect it will send it repeatedly (until there's a comment anyway). If you want to fix it at a query level, then…
-
This depends on how you have set up your user directories. We can't tell you how to re-configure your system without any knowledge of what you've set up.
-
You would need to have a portal for each customer to do this - a knowledge base space is linked to a portal.
-
Yes, it can.
-
You can't do this - the velocity is calculated from previous data. A workaround (which I feel is clunky, and there may be others) is to create a dummy issue for the "missing" 25%
-
JQL is for finding issues, and it's built for that - if you were to try to replicate a JQL query in SQL, you could easily end up with SQL queries with 40+ joins in them. It's not SQL, and does not have the same capabilities. The ways to see the lists of options are * As an admin, look at the config * As a human user, log…
-
You should *never* mess with an Atlassian database if you don't understand it in full. I would go back to the backup you took before you did this, as you could now have corrupted quite a lot of things across your instance.
-
The system administrator account is there for Atlassian to maintain your system. You don't have any access to it, and shouldn't use it. Atlassian are migrating all Cloud instances to use Atlassian accounts rather than local logins, so I suspect that's what you are seeing the effects of. I would definitely raise it with…
-
This is an essay question really. Jumping in at random and guessing at replacing Tomcat (don't - it's a massive effort, leaves you unsupported, makes upgrades a lot harder and almost certainly won't help in the slightest), or tuning the JVM, or fiddling with the hardware is absolutely the wrong approach. You need to define…
-
See https://www.atlassian.com/software/jira/download and try the "all server versions" link
-
I'm most familiar with this using Apache, but you could use other proxying web servers. Apache docs are at https://confluence.atlassian.com/kb/proxying-atlassian-server-applications-with-apache-http-server-mod_proxy_http-806032611.html
-
This is not going to work - you've built up an over-complicated requirement that can't be done without a lot of extra work. A JQL query returns a list of issues that match a set of search criteria. The criteria are applied to each issue independently of the others. It gives you a simple list of issues that match. There is…
-
Ah, ok, well, you can get close to that without coding. I am assuming the "else" is subordinate in this, and it needs spelling out because any issue could fall into one of four classes: * Neither component is on it * HR is on it * CXP is on it * HR and CXP are both on it I think you want to try: Project = Optimus and…
-
No. JQL is not SQL, it's a simple search for a list of issues that match the criteria in it. You can achieve this by providing calculated data to search on if you put a bit of effort into it. You've got two searches in your query, and it's not clear what the "if" is supposed to be doing (where's the "then/else" part?), so…
-
This comes up a lot. The main problem is that the default setup for JIRA lets everyone in, and you have to unpick that to make it work correctly. First, go to the permission scheme and have a look at them. They list the rights that collections of users get in projects. The default scheme grants the role of "users" some…
-
Ah, you're right, the doc is unclear. My familiarity with it made me error blind. You're clicking on "create issue" in the menu, not "create issue" in the workflow editor.
-
Your assignee must be a user. As Joe says, JSD allows for another type of user, the "customer", but for JIRA to work properly, your assignee must be a user. The only "elegant" solution is for you to use it properly, and grant accounts to those who actually need them, either as JIRA users, or JSD customers.
-
created < -5m Will give you "created more than five minutes ago"
-
The document is accurate. Where is it unclear for you?