Comments
-
Oops, sorry, my second line should have been "Find or write your own code...". This is an example of a "find something to do it for you"
-
You'll need to * Use a cascading select field * Write your own code to provide a field that looks at other fields * Write some javascript to link the two fields (strongly not recommended, it's horrid to get right and worse to support) * Use something like the Behaviours functions of the Script runner to insert code that…
-
You can (with code) spawn issues in other projects. Sub tasks always belong to their parent, and hence must be in the same project as their parent.
-
Yes. For automating it, see http://confluence.atlassian.com/display/JIRACOM/Automating+JIRA+operations+via+wget
-
Fix what? You've described what is happening (which is what the docs say it should do), but not what you want it to do.
-
Depends on the permissions the reporter has to assign (or be assigned?) the issue. Ok, so assignee is on screen in the Edit screen, but does it appear for the user that you are running the SOAP stuff as? Do they get the "assign to" link too? Is it definitely an update and not a transition? Have you checked the field…
-
First, no, avoid editing the database - it's a last resort because you need to stop Jira, get a proven backup, run the SQL, restart it, reindex and then test it very carefully. You can destroy a Jira by hacking it's database. If the issues that aren't changing are in the same project and there's a pattern in the issue type…
-
The steps I follow are determined by the setup of the Jira systems being upgraded. All I can really tell you is "test it, make sure you have backups and a solid roll-back plan, and test it" I'd work through https://confluence.atlassian.com/display/JIRA/Upgrading+JIRAto establish the best approach for your systems. From…
-
Yes and no. I've done 4.1 and 4.0 to 6.1 without significant problems, and tried a 4.2 that had all sorts of issues. The difficulty with this question is that every system is different. Just because I had problem X when I went from 4.2 to 6.1 doesn't mean you will run into it. I would expect the migration to be absolutely…
-
That sounds like you don't have the ability to see other users.
-
Ah, ok, thanks for the explanation. I'd call them "tasks" as that's what we get when we're using the English language setup. Atlassian tend to use different words in their systems even when they're often similar concepts (Confluence has spaces, JIRA has projects - they're both ways to logically group up objects so they…
-
As you say "issues", I assume you mean JIRA, rather than Confluence. If so, take a look at the permission scheme for the project. What does the line "assignable user" say?
-
Use a browser with less bugs. IE8 is pretty much deprecated already - MS are only really doing security patches for it.
-
Yes, that's a bug in IE8. I'm not sure IE8 is supported any more.
-
Ivar is right about checking the workflow - if you're pushing the issue through a transition, then I half expect to find that the transition has "set resolution to fixed" as a post function. If it's not a post-function, then you need to check through your listeners. They can update issues when they detect any changes.…
-
Just to add - all of them are "safe". But I'd always tend towards "latest"
-
Frankly, you've done 99% of the debugging here, and actually ruled out a Jira problem! As the user is getting some emails, you know the delivery and transport of mail settings are all correct. You've checked she's part of the right schemes and can see what she needs to Trying it with a test user, who is set up the same as…
-
https://answers.atlassian.com/questions/55128/jira-and-footprints
-
A lot of JIRA assumes that you're not interested in resolved issues, and hence defaults to ignoring them unless you actively choose to look for them. Make sure you set a resolution when closing issues and you'll find you don't see much of them. There are ways you could completely hide them, but then a lot of your…
-
As a project administrator, you need to add components and versions to the project. It's not a global/system administration function, it's tied to the project. Someone with the right to adminstrate the project needs to do this (they'll also have the power to adminstrate project users)
-
You can't do some things with draft workflows. Louise has already answered this question
-
Hmm, is there a pattern as to what it's creating? Let's say: * Alice has commented * Bob is a reporter * Chuck has both reported and commented Then let's say that the import creates Bob and Chuck, but not Alice, then you can kind of assume that it's parsing the import for "reporter", creating them, correctly assigning…
-
To import into the reporter or commented by people, then they have to be Jira users. Two options I've used in the past - 1. Create them as Jira users. Even if the accounts are "dummy" ones that can't log in (dead email address, and don't belong to any groups so they can't do anything and don't count as licence seats) 2. As…
-
I'm afraid that really is what the error message said - it's trying to reach the database over your network, and it can't. Check the network and the database server is running and accepting connections.
-
You cannot do this. Cloud only supports its own internal directory and google apps.
-
I'd suggest you raise this with Atlassian then, as the funds have not arrived, or they've been misallocated. (I am assuming you have checked your my.Atlassian account to see if there are licence keys there and they still say 2015 on them?)
-
Have you paid the invoice yet? You won't get keys until then. You can run on an evaluation licence until you've paid if you want.
-
Log in to JIRA as an admin, and go to Admin -> Licences. Then you can paste the licence key into the box.
-
Are you set up to receive the email triggered by the event? Do you have "email me on my changes" turned off in your profile when testing it?
-
They are the priorities of the issues - check admin -> priorities and you'll see that each priority is assigned a colour as well as an icon and name.