Comments
-
I'd separate them out - it sounds like the project team is not part of the development or testing team, so they shouldn't be directly affecting the work that the dev teams are doing. Give them their own issue type for UAT and have boards that exclude it for dev/test and include only that type for UAT. Or, a cleaner but…
-
OK, there's no way to do that at all. JIRA uses the next free number, and it never goes back to reuse numbers, even if you've skipped them.It's a pretty horrid way to differentiate between hardware and software, it sounds like an inherited bodge from a system that wasn't designed as a proper issue tracker. I'd take the…
-
Generally you don't. Could you explain what you are actually trying to do though, as that could lead us to a better answer than the handful of total bodges I am imagining.
-
There is no version for JIRA 6. I'd recommend upgrading your JIRA so you can use it. You'll want to upgrade soon anyway - 6.4 goes out of support in spring 2017
-
It sounds like you created the account, then an administrator deleted it, then you've added it again, but it has not been added to all the right groups or roles. You should talk to your web dev team to get your new account added to the project and/or your administrator to check your group membership.
-
What do you want from a column in a backlog? A backlog is a list of issues to be prioritised and then drawn into a sprint, or a list of stuff that needs doing (Which, once you've started to look at it, by definition, isn't backlog any more)
-
Go through all the permissions schemes looking for the usage of "Group: anyone". Where you find it, remove it.
-
Make sure the "due date" field is on screen, and the users have "schedule" permission.
-
You probably want to ask this in a Dspace forum, or explain what it has to do with Atlassian products if you still think you should be asking here.
-
It's been merged into the script-runner addon. Install that instead, and you'll find behaviours in it. Check the upgrade notes first though, I seem to remember some behaviours need their config tweaked.
-
The data does not change. The renderers just draw it on-screen differently. So you can swap between renderers without any risk beyond the users writing the data as though it's for the wrong renderer. My other half gave me a good analogy once - glasses. When she and I look at the same picture, we see different things. When…
-
You can log it directly in the Jira you just searched!
-
It's not stated on the site like that, it's just the licecing inside the addon that says "I'm for software"
-
The Subversion add-on is classed as an add-on for JIRA Software now, and hence won't appear in Core alone.
-
This is the same question as https://answers.atlassian.com/questions/52895508
-
Have you enabled Questions in your OnDemand account?
-
That's a DNS type error - your network can't resolve the name you've put into Jira for the mail server. (I'm assuming you've replaced your actual settings with the demo-type strings in your comment)
-
Enable POP3 (although I'd recommend IMAP over POP3), or write something in Exchange to dump incoming email out to files on the Jira server The problem here is that MAPI, the protocol Exchange uses, is proprietary and closed source, and has a significant licencing implication if you want to use it elsewhere. IMAP is a much…
-
My answer still stands - you'll need code to do it. And if you're trying to do aliasing as found in SQL, you will probably need quite a lot.
-
That's not possible - you'll need to do some coding in the core of the search functionality to do that. Personally, I'd question the need as well. "Status = Open" is a lot more clear than "(Open issue)" because the second could be a description or an imperative, and your users are typing "Status = Open" into the query box…
-
Ok, it can't start up fully for some reason. Try working your way throughhttps://confluence.atlassian.com/display/JIRAKB/Troubleshooting+JIRA+Startup+Failed+Error
-
You need to read the log file to find out why JIRA is not running. Look for atlassian-jira.log under the logs directory in the jira-home directory you set up.
-
The error message tells you what line is failing, although the character reference might not be that helpful - it's often "the next thing I couldn't read" instead of "where you've got something wrong"
-
The error message you're getting really is telling you what is wrong - there is at least one " mark in your csv that doesn't match up, and is breaking the format. You'll need to escape the extra " marks in order to import them. I think it's just using "" instead of "
-
You're giving it the wrong name/password combination, or you haven't granted the user access to the database correctly. Go back over the installation of the database side, and check the username/password combination with another tool like squirrel or the SQL Server tool.
-
There doesn't actually appear to be anything wrong here. The log says it's starting. You mention a restart, but there's no sign of that, and you're not telling us what you're doing. Where is the problem?
-
Have you used the optimise/repair option for the ranking field?
-
Looks like the service isn't running at all. Check if it's running and have a look at the log files.
-
It looks like you have hit the wrong URL with your REST call. You shouldn't have had any of that html back, it implies you're landing on standard pages rather than the REST one.
-
No. Why would it? If you're adding an option to the possible list, there's no reason to assume you want to add it to the issues, and even if you did, JIRA has no way of knowing which ones you want to add it to. It's up to you to define what a new option should be added to.