Comments
-
Sounds like you missed the move of the actual database. What database are you using?
-
Ah, I'm sorry, I've misunderstood your licence situation. Service desk will continue to work, but you need to move to a version 2 licence (you should be able to do that in your my.atlassian account - the existing licence you have should count towards it)
-
Where are you stuck in the documentation? What are you doing differently from what it says?
-
Again, when you upgrade, your existing licence will work.
-
Oh, and even if you do decide to upgrade, your existing licence will work.
-
No, that should be available in Service Desk 2.0 and above.
-
Go into manage-addons, find it, and click "update".
-
Sub-tasks need to stay with their parent issue, so no, because they follow their parent.
-
None - you should not write to a JIRA database. That's the short easy answer. The longer one is that we need a bit more information. You've said you've got a field that is of type "database information". JIRA does not have that type of field in it, so it's been added by one of the database field add-ons, but we can't…
-
Not really, it usually requires custom code, and you can't do that on Cloud.
-
Yes, you can do this. I would: * Copy the existing workflow, and call the copy something like "hosting workflow" * Edit the copy - look for the "create" transition and change the landing point for it from "open" to "in progress" (Actually, you might want to be a bit more radical and have a completely different workflow,…
-
I don't think this is right - first, to use Simplified workflow, you need to have the Agile plugin, and second, the simplified workflow still creates issues in the same initial status.
-
Ouch, shouty. Version 6 and below still have that column. You should read Jamie's link to see what is changing here.
-
No. Atlassian do gather numbers on support calls, but this is not going to be representative of all the installations out there. You can't rely on licences because a licence is either valid up to 3.13, or it's valid from 4.0 to the latest version, so you can't even say "we've got X licences on version Y" - all you know is…
-
You can write a post-function to do it as well, but the script-runner is probably going to be easier.
-
It's a technical challenge - there are (or were) a couple of plugins that support differing licenses. Obviously, they require Jira to have the same or more users, but they implement a "user must be in group and group must be of maximum size" rule. I don't know if they're still around though, or if anyone does them. Some…
-
No, it went paid a couple of versions ago. You could use the old version, but it won't work on Jira 7
-
I tend to agree with Bob on this one, having a separate workflow for each project is a nightmare to be avoided whereever you can. Similar projects should use the same schemes and share as much configuration as possible. In this case, I'd go with at least line 1 on this list, combined with some of the others: * No, I'm not…
-
I'm not sure it matters whether its a standard workflow, I tend to agree with Bob - it's not a good practice to use multiple different workflows across multiple projects. It IS good practice to use the same workflow for all projects that work in similar ways.
-
I think my point is that REST is not for imports, never has been, and never will be. The difficulty with the importers I think is that you're asking Atlassian to code for every single possible import case, and even if the JIRA issue system could be mapped in a way that replicates any arbitrary other-tracker-system, it's…
-
There was one thing that jumped out of that which made me want to scream "no". There is no way the REST API should not follow the UI. You set up a workflow, control the fields, set the screens and so-on, and then a user happily bypasses everything with a REST call. No, no, no. Absolutely no. However. You are (mostly)…
-
I'm sorry, you still have not told us what you have set up in terms of incoming and outgoing emails? What are your users doing that breaks it?
-
I'm sorry, but that still does not explain what you are seeing, what you are doing or what you are expecting.What does "no subject provided" mean? Where are you seeing it? What's "unable to read description"? (It's a field, it has data, if you can't read it, you shouldn't have put bad data into it). What are you trying to…
-
I'm afraid your question is too confused to make sense of. I can see that you're an admin on JIRA 6.2, but beyond that,I am sorry, but I cannot follow it. Could you explain, in simple short sentences, what you are doing, what you expect to happen and what is actually happening?
-
Your thoughts on "temporarily use a scheme where all fields are optional" are exactly what I would have done straight away. There are other approaches, but that one is by far the most simple, quick and intuitive. The only drawback really is that issues that are missing mandatory fields will demand them on edit or…
-
As I already said, there's nothing there to do that. You can do some coding to write something to do it, or maybe use SQL to change them all to something which would force everyone to use the "reset password" link (If you are going to take that route, bear in mind that you NEVER alter a Jira database without it being…
-
Depends on your user directory setup. If it's the internal Jira one, then that is quite simple and doesn't have that functionality, so you're stuck. If it's an external one, then you might have, but it depends on what you're using.
-
Could you explain what you mean by "issue details are going down" and maybe show us where you inserted the <br> in the template?
-
No, that's wrong. "Edit issues" is a specific line in the permission scheme. It's certainly not a global permission, and there's no overloaded semantics, it's a single clear line.
-
Not in JIRA Core, but Software separates the permissions out when using boards