Comments
-
The first of those links parrots the "use apache in front of Atlassian doc".
-
I think you'll need to name the list explicitly, one clause at a time. labels != foo AND labels != zing AND labels != bar AND ....
-
You do know that "this instruction" simply parrots the Atlassian documentation? It's wrong for Jira 7.3 because of the bug Andrew mentions, but that's the exception.
-
Have a look through https://confluence.atlassian.com/jiracorecloud/creating-issues-using-the-csv-importer-765593817.html
-
A forum with Atlassian systems is probably best done with Confluence, with either the "Questions" add-on or the "Community Forums" add-on. I would evaluate both, separately.
-
Thanks Andrew!
-
Don't know. What is a "Bug Serial number"? How are you entering or creating it?
-
I don't know! It's your system! I can't tell you what you have configured. I would guess that your admin should have set it up as a custom field of some sort, then your script will have to update that field.
-
Running Jira as root is a VERY bad practice, and you should not do that. You should reconfigure the security on the linux box to allow the Jira user to use port 80 instead, or use the security tricks Apache does to do it. Or better, use a proxy instead. Anyway, I suspect you are running into firewall or security issues…
-
duplicate of https://community.atlassian.com/t5/Questions/Problem-to-change-tcp-port-in-server-xml/qaq-p/681756
-
I can see it under "update field" when choosing a post function.
-
What formats can you export GrooveHQ data into? Does it have an API you could use to scrape data out of and then poke it into Jira over REST?
-
It makes perfect sense. Deleting a project can only be done by administrators. Users, in a few cases (see points above about why you should generally disallow delete), should be allowed to delete issues, without needing admin rights.
-
How are you doing the "export to excel"? Can you show us a screenshot of the top few rows of the issue navigator including the field headers? Does the timetracking field on the issues show correctly?
-
Nothing happens. The server licence and cloud subscription are two totally separate things. If your server licence was bought within the last 30 days, you can get a refund. If it is older than that, you can't. If it is two years old and you have not renewed, then it's completely irrelevant as it expired a year ago anyway.
-
There is something not right here, and all I can think of is what Jobin has said - there's an addon we need to know about.
-
I'm sorry for being so slow to respond, I've got a block of work stuff in the way. The Cloudshare environments are built for your course, and shut down after your training days. I am not sure what you are looking at though. Could you explain what your course is, and what your instructors are telling you about the…
-
No, I am sorry, there is no free solution, you need add-ons to do this, or remote scripting.
-
You have almost answered your own question. A Service Desk portal shows requests from customers. A request is an issue with a layer of extra customer-facing stuff on top. You are moving an issue from a service desk project to a development project. That means it's no longer a service desk request, because it's in a…
-
A requirement to check carefully is the version of Java - I'm not sure the old version you need to run Confluence 3.3 is going to work on Windows 10 (and even if it does, you should only use it to perform an upgrade as both Java and Confluence are totally insecure and should not be used)
-
Why duplicate it all in Confluence again? You're creating the issue from a page already, so surely you already have some data that you are working from? (And Confluence is not an issue tracker, it does not have issues/tickets)
-
You can't do this. A webhook happens in a workflow if you tell the workflow to do it. If you then use the workflow in a project, the webhook will (try to) do what you told it to. There's no way to arbitrarily not do it on the basis of something unknown. You'll need to use Jira as it was designed - have two workflows.
-
The select searcher.
-
There's a slight problem there - the "type" of a scripted field is "a scripted field" There's nothing ScriptRunner can do about this, and not a lot Jira can either - it's the way Jira has to handle custom field types. Your only option over REST is to check if the content returned looks like a date.
-
Text search does not support the = operator. It's also the wrong searcher to use for a select list type field. You could try an "exact text searcher" instead if your field really is text - there are a couple of add-ons that provide one of those. Or s a select list searcher if it's really a list of options.
-
Ok, check the field configuration next. Is the resolution field valid for the project and issue type?
-
That's correct. Description is for a human to describe something, and should not be defaulted. When you do default it, you end up with metric shed-loads of identical and pointless descriptions completely wasting everyone's time, and when the users do enter data, it's not very categorisable when you search. A far better…
-
Jira does not do this column splitting.
-
Might be worth asking this in https://community.developer.atlassian.com/ as well - they code external stuff a lot.
-
There's an obvious question of "why?" here - for what reason do you want to restart it? There are good ones, but if it's not a good reason, your time would be better spent fixing the real problem. Anyway, there is a simple trick - schedule "stop jira" for (say) 1:05 and then "start jira" for 1:10.