Comments
-
You need to reconfigure your network to allow the outgoing connection to the marketplace servers.
-
Yes, because you've not allowed it to connect.
-
Your Confluence cannot reach the internet to check the supported versions. To get rid of the message, either allow it on to the internet, or disable the attempt to check by the workaround in https://jira.atlassian.com/browse/CONFSERVER-45560
-
>an Epic is selected in a work package That mandates a listener then. Start at https://scriptrunner.adaptavist.com/latest/jira/listeners.html - you'll want it to catch issue created and updated events.
-
Cloud is automatically the latest version. You do not upgrade it. See https://confluence.atlassian.com/support/atlassian-cloud-update-policy-269193828.html
-
Cloud seems to be having some problems today, all we can really do is suggest you follow the instructions in the error message - give it 10 minutes, click "try again" and if it still does not work, raise it over at https://support.atlassian.com
-
Ok, the best way to do that is from the other end - on the "create" transition in the workflow, have a post-function that sends information over to your application. If you have to do it from the outside, then you'll need to write something that polls JIRA with "project = X and created > 'last time I looked'" over the REST…
-
Ah, other people are able to use the same url ok? If that's the case, then there's something wrong with your browser. Try another one, or try clearing the caches, cookies and history etc.
-
You can't do it. The last column is all that matters. The best you can do is move the "ready for merge" status into the "done" column. This will cause the next problem in that you can't move issues between status within the same column, but I'm sort of expecting that you would be doing that for a batch of issues with "bulk…
-
No. Cloud is automatically the latest version, you don't have to do anything.
-
That happens in two cases: 1. You really have given it a broken url - are you sure the url is correct? Just to check something, could you try it with just the base url (drop the /issues from the end) and see what that does? 2. The service is running, but the JIRA application has failed. You'll need to get in touch with…
-
That's not an upgrade, it's a move. Cloud is generally ahead of Server versions, and sadly, the two systems are diverging too, so it's becoming a lot harder to say "Cloud version X is equivalent to Server version Y" The documentation for this migration is at…
-
There's two parts to this answer 1. What do you want from "monitoring"? 2. What does "continuous" mean in this context? The REST API for JIRA is best thought of as a pull process. You have a system which asks JIRA questions or gives it commands by firing REST requests at it. This can never match the dictionary definition…
-
Yes, but your users will not find this particularly usable and are quite likely to put rubbish in.
-
Confluence isn't designed for user tracking, but it does store "user logged in" information against a users' profile, so you can just check that to see if they've logged in.
-
No, JIRA needs to know what the issue is in order to create a comment on it. As the "reply to" code is currently broken (as per the bug report you've found), the only other thing it can do is look for the issue number.
-
If you're using plain JIRA with an issue type of "test" then this is a function of your workflow. You'll need your admins to amend your workflow, and/or permissions to allow you to do this. If it's not just JIRA, then could you explain a bit more? What's the testing add-on? And is it even JIRA?
-
ScriptRunner is probably going to be the best way. Otherwise you'll need other add-ons to create scripts or provide functions. Next question though - when do you need to do this update and how? For example: If you just want the cost on the Epic to show in the work package at all times, a scripted field is a good option If…
-
There's more than two ways of indexing. It's not quite this simple in reality, but unless you're coding, this is the easiest way to think of it: * There's a chunk of code which reads the index for an issue. * There's a chunk of code which reads an issue out of the database and creates a set of index entries for it, based…
-
I understand that, and you don't need dbo privileges for the bitbucket user. But you do need to give it full access to everything within its own database/view. It's not trying to access anything outside its scope. It needs to be able to use create, drop, update, index and so-on inside its own area. Have you checked that…
-
I agree with Robert, a space per project is most manageable. Your users will understand it, as the concept is intuitive and enables them to think and see things in terms of "this project". They're natural containers for projects in most cases. I would not wory about having too many spaces. Confluence handles it fine, as do…
-
Technically, a big number. Before you reach it, your field will have become useless to the user, and the browser will struggle to render it.
-
What scripting add-on do you have to do this with?
-
Mostly, yes, but the last couple of sentences are not quite right. Rather than try to explain that in a twisted sort of way, it's better to try to show you what is going in behind the scenes. JIRA has a workflow that your issue is following. It's a string of status with transitions between them. Let's imagine you have a…
-
The only mechanisms boards have for changing the status are: 1. Drag the card into a column 2. Open the issue up in full view and use the workflow buttons So, you'll need to add a column if you want to do this from the board. If you're happy going via route 2, then you could edit the workflow, adding a post-function to set…
-
As I said originally, Service Desk runs on top of Core. If you've installed JSD, Core is already running behind it. You're done, you don't "install Core as a complete application", it's already there, and you have the complete functionality of Core. One of its functions is to run applications like JSD
-
I think you've misunderstood the point. You can't answer the question "what is the current project" when you're on a board that includes more than one. There is no "currently selected project" when you're in a board, because the board might have more than one. The only time "current project" can be answered for a board is…
-
But that could easily lead you into a situation where two users get totally different boards when they're looking at the same one. The context matters here, and the boards can not give you that context. The function would need to return "null" when used in a board.
-
No, there's no function, and I'm afraid as a generalisation, it would not work, as the concept of "current project" only applies in some places. Imagine the JQL as asking the question "what is the current project?". If I go to a board that has a filter of "project in (A, B, C)" or "issue type = bug", what is the current…
-
I don't think "ask support every time I want to run a query" is a good solution myself. It's good as a one-off investigative task, but there's every change you'll want to add projects with similar schemes. Sorry Brendan. Apart from the two possibilites I suggested already, your mention of "project specific thing" triggered…