Comments
-
JQL is for finding issues, it doesn't do anything with them. You need to find/write something that will create subtasks on an issue (have a look in the marketplace) when you do something with the issue - a common one is to create subtasks on a transition (if you do that with your workflow, then you can use JQL to find many…
-
No. This is pretty much nonsense for any web-based application. When you serve up a page, the browser gets a load of stuff to interpret and display. That MUST include the contents of a page if you want to give it to the user, and hence, because the user's browser has it, they can do what the heck they want with it,…
-
Depends on the problem you're having. Is it surrounded by an "unmigrated wiki markup" macro? That implies the upgrade process was unable to translate wiki format into the new storage format. Or is the content correct and just looking different? Or is it surrounded by / using other macros?
-
Yes, it works the same as if you had a full licence.
-
A couple of places have a "bin" project which you move "deleted" issues into as well.
-
Well, I was going to wave you at the standard Jira knowledge base article on this, but Atlassian seem to have deleted it. Anyway, this is often down to slowness, so here's a quick list of things to look at initially: If you were on a Windows box then virus scanners are notorious for breaking services like this What version…
-
I've already answered that. (Of course, you also need to be sure that the spreadsheet has been saved in a format your version can open)
-
Yes, spreadsheets work fine on Macs
-
Depends on how you are defining "blocked"? Is it via linking?
-
Ok. I assume you will be commenting via REST, as you can't do it with SQL. Ideally, you should probably be fetching the data with REST as well. (Or you could just use the script runner to do this and do the whole thing internally instead) I also suspect your criteria are wrong. You probably need to exclude…
-
I'm sorry, I still don't understand. I understand that you want a Jira ID and the name of the person who created it. But I don't grasp how the 15 days criteria is attached to it. Do you mean the issue has not been updated in the last 15 days? There is actually a problem with "creator" too - Jira allows a person to create…
-
I'm sorry, but that reads as you want to report on people who have not changed their name in the last 15 days? That doesn't sound useful, could you explain what I have misunderstood?
-
You can make them public by exposing the systems to the internet and allowing "anonymous" access to the projects and spaces you wish to share (I would not recommend letting anonymous do anything other than read though) If your product is completely open source, you could also apply for the Open Source licences for the…in Is it possible to make any of our licensed JIRA board and Confluence Page public for our open source project? It will help us open source our project tracking process and not just the codes. Our organization already has license for atlassian products Comment by Nic Brough -Adaptavist- January 2016
-
The standard answer is "when it's ready". You won't get anything more accurate than Suren's answer until it's closer the time, and even then you'll never get a specific day until it's actually released
-
I wouldn't do that, it won't get you anywhere. The licence count is "everyone who can log in". Both types of admin, and normal users. To see these, go to "global permissions" and look at the "Jira Admin", "Admin" and "User" lines. That tells you what groups of people count towards your licence. But it only counts each…
-
The systems I look after are all fine.I think you might be talking about Cloud - we're not Cloud admins, we're a community of end-users...
-
The error is telling you that the user is not there - that's the check for whether they exist!
-
This is exactly what is supposed to happen. Agile considers issues "done" in the done column and only allows done issues in sprints as they close. It tries to be helpful by moving not-done issues into the next sprint because that is what you should do. You need to clear up your understanding of "done", or not create the…
-
This is exactly what is supposed to happen. Agile considers issues "done" in the done column and only allows done issues in sprints as they close. It tries to be helpful by moving not-done issues into the next sprint because that is what you should do. You need to clear up your understanding of "done", or not create the…
-
I'm sorry, I still do not understand what you mean by "Group Administrator rights". This is not something that Jira has. System and Jira administrators can edit groups, no-one else. Could you explain this before we go any further, because if I don't understand what you really mean, I could tell you very wrong things.
-
No, it's a lot more granular than that. System admins have the right to change system settings, but that's separate from Project admin rights (although a lot of places blur the lines or merge them by saying things like "if you're in the sys admin group, you get project admin in these schemes too") * To maintain versions, a…
-
You can start with JIRA Core and add Service Desk and/or Software in either order. You can start with Service Desk and add Software, or start with Software and add Service Desk. The last option is generally the recommended one for a new starter because Service Desk is less complex than Software (in terms of how much it…
-
I think it might be because links are directional. Let's say you link issue ABC-123 TO issue ABC-456 with a link type of "depends on". So 123 "depends on" 456, and 456 "is a dependency of" 123. Another way to say it might be "ABC-123" is the "source" and "ABC-456" is the "destination". So, when your code iterates through…
-
You can't. The fields are text, if someone puts something sensitive in them, that's up to the user. The only thing you might be able to do is write or find a validator which can scan the text and return a failure message if they enter something you don't wnt them to. Of course, what they might enter is so variable, I don't…
-
1. I don't understand this - Jira allows you to look at issues. That's what it's for. You just look at the issue. 2. Not really, because you just look at an issue. If you want to do remote work, then look at the REST API - that's exposed and usable in OnDemand 3. Jira handles thousands of issues. I've used it with 200…
-
For what? That's the public issue tracker. Read it for yourself. I'm not going to sit here reading through a list of stuff to pick out for you when you could do it yourself.
-
Yes. See https://jira.atlassian.comand select the Jira, Stash and Bamboo projects.
-
The question you refer to has a correct answer. You'll need to explain why it doesn't work for you, and what you have done differently to what it recommends that has stopped it from working.
-
Hmm, that sounds like there's a problem on Cloud. I'd raise that with Atlassian support, because it looks like you've done everything right to me, and it's the Cloud JIRA falling over.