Comments
-
Smoked roasted corn on the cob works for me Then I skewer whatever vegetables I can find and roast them with large slabs of halloumi which then goes into a wrap or pitta with chilli hummus. Washed down with chilled craft beer. (I'm one of those "difficult to cook for gits" sometimes called "vegetarians")
-
The examples are curl commands you run on a command line.
-
My guess is that it has removed issues from a board, not the actual issues themselves. Check the board configuration, I suspect the board either excludes the new status of the missing issues, or the status is not mapped in the columns.
-
Jira has quite a lot of functions you can use over REST. I could point you at the REST docs, but I find them dry (they are reference material, rather than practical) However, the best way to get started with REST, I think, is to get straight into it. I would create a test project in your Cloud system so you don't mess…
-
There's no way to remove the option without doing some coding, but @[deleted] has given you a really good way to stop the users doing the wrong thing.
-
If you download the source code for the applications, you will see that they have standard tests alongside the core code, built for automated testing. However, Atlassian cannot test the add-ons, as there are thousands of them, mostly being updated regularly, and they don't own them. You will need to build tests for your…
-
It's the "project name" field, but yes, that's exactly the problem. That field is not on screen, but it is mandatory. Either get the admins to remove the mandatory flag, or get the field on the screen so you can fill it.
-
Any method you use to do this properly is going to either be slow (because you throttle it) or cause performance reductions as it takes resources. I would also try testing an external REST based script for speed and performance, and if you have ScriptRunner, that as well. I once wrote a script that looped through issues I…
-
You need to get into the project settings. You do not appear to be logged in as an admin in your screenshot,
-
The anti-spam robot is not 100% accurate, it's probably the code, image and what might be links all adding up to look like possible spam. I've just un-spammed the posts.
-
Wow. You really care about this, but still completely ignore almost everything that has gone before. The only part I picked up on as new was "That you think John was failing to address what you saw as the core point under consideration is actually a sign that you were confused about what the point actually was." But you…
-
Problem is, he's wrong. He has not read and understood the previous postings. His last essay on the subject was well-formed, but totally missed the previous points. Anyway. You are a lot closer to seeing the right way to do it, but you have missed a layer. It's not about you being in a particular role, it's about…
-
A dashboard is probably going to be the right answer, but it is hard to tell from just "the status of all integrations". What are these "integrations"?
-
I am afraid Jira only has one estimate field. To do separate ones, you will need to create new custom fields to catch the three types of estimate and then find or write some code that can update the estimate field whenever any of the three fields changes.
-
Where are you getting this? I ask because if you're using Cloud, or an external directory on server, then it's not up to you to set the name, it's up to the user system.
-
What do you mean? All users have a field for a display name.
-
"Everything else" is usually a swimlane that catches all issues not caught by other swimlane definitions. Go to board admin -> swimlanes and have a look at what you have defined for them.
-
It definitely does support it, that's pretty much what the backlog is for.
-
Kanban boards have a "secondary filter" or sub-filter which is for hiding issues that are "done, don't want on board any more". The default filter for them makes anything with a fix version done. You will either need to amend the sub-filter, or remove the fixversion from the issue so it no longer matches. It's probably…
-
That document is wrong, not you. All the later versions have been corrected and say just "Jira Administrators"
-
That's not quite right. Jira Administrators and Jira System Adminstrators both have full access to create, edit, manage and delete workflows. I think you meant Project and/or Board administrators - in some cases, they can make some restricted changes to workflows.
-
I don't see how exporting an email to a file helps anyone "check outgoing messages". I would also question what they are "checking" and why? If they want Jira to send the "correct" message, then don't mess with the email, just put the right data into Jira so you know it will send the right thing. This really does sound…
-
The edits made it worse! The old text was Hi have made payment through bank and sent email to remittance@atlassian.com , when will i get invoice and licence .?
-
Pictures are of no help when you lose the data in them. I don't know why people bother with them, when it's plain you lose so much. Please, just the full text of the error, minus the user name
-
Not impossible, just that you have to export and import.
-
Drag and drop will work, as long as the board is configured with a filter that says "order by rank"
-
It would have helped if you had told us you had a plugin that was deliberately mangling the outgoing emails into a file format, making them useless as emails. I do not understand why you are doing this. If you don't do it, and use email as intended, you won't need to do any translations or parsing. It sounds like you are…
-
There should be no limit, I've got several pointing at a single project. It sounds like the handler for bug can't retreive anything from the mailbox
-
The only way to do it without add-ons is to hack the core of Jira, effectively implementing what an add-on would do in the core. An add-on is easier, faster and safer than that, plus it leaves you supported if something goes wrong (Atlassian don't technically support add-ons, but if you have a problem, you can temporarily…
-
Impossible to say with the important bits of the error message missing. Could you give us all of the error, in text (delete the name of the user if you want)