Comments
-
I use the rss feed, so it doesn't get lost in email.
-
This is Morticia. If you look to the right of Morticia, there is a photo of Esk and I in much the same place from a couple of years before. Esk died a 15 months ago, (at around 18 years old, a good run for a rescued domestic moggy) hence making space for us to rescue Morticia. And, no, we did not realise I would be able to…
-
The basic search does not have functionality to preselect arbitrary options, so no, you can't do this. I would embrace the advanced search, as @Sreenivasaraju P suggests.
-
You'd need to look at the docs for your "client" - BasicIssue is something it is doing, and if you want it to do something else, you'll need to use whatever the client API provides. The REST API will not give you an object though. My best guess is that your client thinks of BasicIssue being the core of an issue, created by…
-
You will need to put a groovy engine into your plugin in order to support running groovy scripts. Apps like ScriptRunner already do this sort of thing.
-
Oops, sorry @Scott Dudley _Cenote_ - thank you for the reminder!
-
Ah, no problem. Go to the project the issues are in and look at the admin section. Look for the "issue type screen scheme" and go into it, then into the "screen scheme" for the issue type that is missing the field. You will find it names "screens" for create, edit, view and default (default is used if any of the others is…
-
You have answered your own question - your system admins will need to do it. We can't help you here - we are end users of the Atlassian software, not your administrators. We have less access than you do! Note that if you're on Cloud though, you don't have System Admins - the role is performed by Atlassian, and that macro…
-
Ok, so if it's on create, that suggests it is an issue field. If it's called "work description", it's not a standard field so it must be a custom field. Given that, it sounds like you have got a field called "work description" which you have added to the "create" screen for the issue type, but not the view (and possibly…
-
You will need to get SOLMAN to issue a REST call that tells Jira to transition the issue from one status to another. We can't really help you with that - it's coding in Solman, not Atlassian.
-
Not in plain Confluence, but there are a couple of Apps on the marketplace which can do it. I've used the Arsenale Lockpoint one in the past, but I'd recommend checking all of them for yourself, rather than rely on my (slightly old and creaky) experiences!
-
The problem with that is that you only get one vote. If one of the users sets the field to yes or no, it is set. For any issue, the value will be empty, no or yes. The voting "field" in Jira accepts votes from multiple users. So any one issue could have 0, 1 or thousands of votes.
-
Correct, this is a seven year old question and is now irrelevant - I'd recommend asking a new one (although the answer is going to be "make an unsupported change to a properties file that will make your Jira less friendly to people who have used it before")
-
It sounds like you did not add a transition from the current status to the new status you added when you edited the workflow. Or if you did, it is protected with a "condition" that prevents you using it.
-
Your mileage will vary, I never said it will fail on everything - it depends on the config of your incorrect url, how you're doing it, if you've got rewrites set up and other stuff. You can make some of it appear to work ok. But not all of it. You are always going to get the error message. Synchrony will fail. Some gadgets…
-
Where are they placing this "work description"?
-
You should be using Jira on a single base-url - it does not function with two.
-
No. The service runs on one url and expects to be found on that url. You can serve it up on others, but it will fail for a lot of actions used on the non-base-url and functions like outgoing email and some links will always take the user back to the base-url based one. Not catastrophic failures with damaged data, you'll…
-
One thing the anti-spam robots don't like much is code. They're not clever and struggle to tell the difference between a good block of code with a problem or a solution, and a block of text that's trying to make it look like not-spam or malicious code. I've told it your question is not spam.
-
A "soft link" is done by your operating system, and depends on the file system underlying it. Unix file systems almost all support simple and effective links, but Windows ones are usually too primitive and require you to do kludgy harder links.To do it on a unix-like systemMove the directory you want to relocate: mv…
-
That is one of the more common reasons for the h2 database catastrophically failing. But Tomcat wouldn't scrub anything, your data should all still be there. I'd scan the file system for .zip files that might be backups, you might be able to rebuild a Jira system if you can find one.
-
Projects are containers for issues, an issue can only be in one container at a time. Jira does track the old issue key, so you can still find it with that, but after the move to another project, it is part of the new project, not the old one.
-
So, it is starting up, suggesting that there is moderately valid data in it, and you can get to a log in screen. Next step is to read the application logs to find out why you can't log in. What are the warnings about the failed logins?
-
It means what it says - the Jira server is not responding to requests from the proxy. You'll need to have a look at the Jira server to see why it is slow and non-responsive.
-
With whom? We're a load of end-users of Atlassian software, I think your question is probably aimed at an employer? Even if that is Atlassian, their policies vary a bit by country, and we're not Atlassian so we don't really know.
-
I would look at the installation document and search for the word "context". To be blunt, we're not here to read this stuff to you, there is perfectly good documentation that answers all of what you have asked so far. By all means ask if you get stuck, but please at least try to read it first. If you do get stuck, please…
-
A vote is a single flag - either you voted for the issue, or you did not.
-
No, it's not. There are a pile of JQL functions built into Jira Core, and Software and Service Desk add more that are related to their purposes. See https://confluence.atlassian.com/jirasoftwareserver/advanced-searching-functions-reference-939938746.html for the built-in ones. ScriptRunner does add yet more JQL functions,…
-
Yes, there are backups, but it's probably not quite what you are imagining. Atlassian take backups of Cloud which are suitable for their disaster recovery. If they lost some or all of a Cloud data centre pile of servers, the backups are suitable for getting all the affected systems back. They are not suitable for…
-
In theory, I know where they're coming from - in an ideal Agile system, you'd have a project and a board for it simply containing everything for that project. In real life, a LOT of Agile teams in the world work across different projects at different times, so cross-project boards instantly make perfect sense. Even more so…