Comments
-
This does not change my response, you have a firewall if you are using ufw, and that is blocking it, or, Bamboo is not running, or your network is not routing the request to the bamboo server
-
7.11.1 - the pom should contain the version you are writing for.
-
This is an old post, and an answered one. You're very unlikely to get any help here.
-
Actually, you can run both for a smallish number of users on a machine with only 4Gb RAM. (For up to 100 users, 1Gb RAM each will work, although I'd be looking at 1.5 well before I got to 100 users). They don't need that amount of memory until you start to put significant load on them.
-
You say "Our receive connector MessageRateLimit is unlimited". I'm afraid you are misinformed. It is limited. The error message coming back from the mail server states that. There's no other way to get that message.
-
Have a look at the links Bob gave.
-
You can with apps that provide one (or scripting functions)
-
I'd guess the default scheme was edited from the admin section.
-
If you're "enabling port 8085 via ufw", then there is a firewall, irrespective of your network type. Connection refused means that the ip:port is blocked by a firewall, or nothing is running there.
-
If you highlight the word or phrase with the cursor and then hover over it, Confluence allows you to add an inline comment at that point in the text. You can then mention people in it to notify them that you need more input.
-
Ok, you are definitely using two different fields. You are putting data into a custom field called "associated project component" and expecting it to appear in a totally different field. If you want the components to add up, put the data in the components field.
-
Try adjusting the url to see it.
-
You can't re-arrange that screen without hacking Jira Software
-
Technically, it's "compatible" in the sense that it will not break. But it can't possibly do anything with ScriptRunner either. It's a bit like saying a screwdriver is "incompatible" with a freezer if you put it in there. You can freeze a screwdriver if you want, but it's not going to do much to help you cook your dinner.
-
It's a bit more complex than I think you have described. I could just say "no" to answer your last question, but I think it is worth explaining what you are looking at. We all know we have a Jira system, providing issues, projects, users, workflows and so-on. This includes a GUI front end for us humans. This system has a…
-
Their "access" might not have changed, but one of your administrators has flipped the "inactive" flag on their accounts, so they can no longer get in or appear in most selections. You will need to go to user maintenance and re-enable the accounts
-
Should be even more to the left of that blue up-arrow than everything else on the screen.
-
I often run into places yelling "let's go Agile" and then realising that they have no idea what it is. Then when we've got past that (and checked that it is actually useful to them in their field, because it's not always right), the even more difficult task is working out how to get it implemented. There's already…
-
In terms of end user experience, it's no excuse. You're already confusing and irritating them by blocking them using a particular issue type in this way, irrespective of the order you reject them in. That's not a good use-case and hence it's pretty much irrelevant in terms of usefulness of ordering validators. If you stick…
-
That's mildly efficient, saving you some CPU cycles, but you'd waste far more cycles implementing something to let you move them around. You really don't need this, it's irrelevant. Your validator will work fine, where-ever it is in the flow.
-
This sounds like one of your administrators has been renaming status without considering that they might be shared. To confirm this, first check the issues that have "changed with no user action" - if there are no status changes in their history that reflect what you're seeing, then it can only be the name changes. Second,…
-
The problem is that the pie chart will be making requests on the base url. I've got the code (because I've hacked it for people a couple of times), and it simply does not use anything else when it goes out to the network. That means there is something on your network changing that request.
-
They've been deleted, so no. Why are you making obsolete copies of data in "your database"?
-
That is what I said, yes.
-
JQL finds issues, not boards, and board id is not a field. Could you explain what you are actually trying to do here? Not ask about a "how do I get technical thing", but what does the user want to get as a result of your actions?
-
No, it's the other way around. The simplified workflow allows project/board administrators to add status. If you move to a new workflow by creating new schemes, you will disable that function. Your boss has given you admin rights. Your best option is probably to use those to give yourself project and board admin rights in…
-
That is something you need to decide within your processes. If you're going along the Agile lines with Scrum or Kanban, then the usual idea is "people prioritise stuff, there's a known pile of stuff that needs doing, developers would grab the next one from the pile as they feel is appropriate". That does rely on you…
-
JRJC is a library written for Jira. ScriptRunner adds other functions that the JRJC cannot possibly know about. So it won't have anything to do with those functions. But it is "compatible", because it talks to Jira and SR doesn't change what Jira exposes to it.
-
You can't with watchers, the point of them is they are external to the project but have at least read-only abilities to see it. For Reporter, add "reporter" to the browse issue permission. Two caveats * This opens the project to a lot of people as they might be a reporter at some point. But they will only see stuff they…
-
Yes, you need Jira admin to be able to define a workflow. In your screenshot, you have not created new status, you have added columns to the board. If you look above the column definition, next to "add column", there is a greyed out "add status" button. You need to use that, but it is greyed out because you are not a board…