Comments
-
Check the workflow for the developer's subtask type. Look at the "event" it fires when the devloper finishes and completes. Make sure the notification schem includes the QA people for that event.
-
You don't. Those two urls are doing very different things. One creates a Request, the other an Issue. Even if you could re-write the url (which you can't without either messing with proxy settings or hacking JIRA core code), you'd give yourself a problem, not only would you be making your portal redundent, your customer…
-
Ok, as you're on Cloud, where we can't read the logs, I think you'll need to ask Cloud support on https://support.atlassian.com A failed test tells me there's something wrong with the config for the mailbox you're trying to connect to, so check the server, user name, password and port that you are giving to JIRA carefully,…
-
Your error message implies that the custom field you're reading is not valid for the issue type you are running the script against.
-
Ack, sorry, yes, I looked to the left when I saw you are on an old version and didn't go as far as "more". It's definitely not the most recent version. That has the dots on the right.
-
You are on an older version, which has the "actions" menu next to your workflows. It was moved to ... on the right only a couple of versions ago.
-
No, you did not. You asked what the differences were. That document is a useful guide to the main differences, so it answers the question you asked. Your new question can also be found with search engines very easily. But you'll find that Server is a system you run yourself (or ask a provider to run for you) and Cloud is…
-
Run the query and look in the url bar in the browser. But if you're "pulling" the data, you probably mean you want a copy of it in a format for a computer to read rather than a web page. See https://developer.atlassian.com/jiradev/jira-apis/jira-rest-apis/jira-rest-api-tutorials/jira-rest-api-example-query-issues
-
Behaviours have nothing to do with this. The snippet is a post-function to give you the basic code for copying from summary to another field. You should be able to adapt it for your needs quite easily (loop through your list of issues that need changing and running the snippet on each issue. An "if" statement on the issue…
-
The licence for an add-on must match the highest tier application you have. You've said you have 50 Service Desk users and 10 Software users. That means your licence for add-ons must be for 50, as that's the highest tier. Separate servers could work, but you'll be lacking in functions linked to SD.
-
Point 1 is the answer. You have not got the field on the "create issue" screen.
-
That's already captured in the requests automatically, and can then be used in the SLA/Queue definition.
-
This would require coding. At a minimum, it would need you to hack the user screen to provide a method to add the internal "user properties" (which are only visible to admins and code) To do it properly with real fields, you'd need to code a back-end to store the data as well, and expose it when you need it.
-
Generally, yes, it is. The importer in 7 is a little bit more robust than the ones for 6, but we've found it can quietly lose data if you try to import from xml created by 5 or 6.
-
Most of the stuff about older versions of Confluence has been archived, but you should find some stuff on Atlassian's docs pages for it.
-
Oh gods, it looks like someone put your home directory in the installation. Forget an upgrade in place, that's not going to work. You should create a new, clean 4.4, export the 3.13 to xml and import it.
-
You do know there are search engines on the internet? Ones that will tell you far faster than we can to start at https://confluence.atlassian.com/cloudkb/pros-and-cons-of-cloud-vs-server-691011844.html
-
Oh, wow, that's an interesting one. It implies that your user system is returning a lot of rubbish to the system you are trying to connect. If anything, I'd say it was expecting a simple string like "failed login", and it's tried to return an image of something! Could you clarify what you are trying to hook up here? It…
-
The page history has a way to compare all changes in each version. It does a simple red/green (with strikeout) to tell you who removed or added stuff. You can revert to versions, but not individual changes (although that's improving as the concurrent editor is improving)
-
You can, but I don't know how it will help. You've not established what the atual problem is. You need to look at the errors in the logs at the time you try to log in - explicitly test a user and enter the wrong password to check that you get something similar to waht I got in my security log (or another error)
-
There's a link to the download archive on the main "download" page. See https://www.atlassian.com/software/confluence/download-archives Bear in mind that if you go too far back, you won't be able to licence it, as the licence format changed. I think it's Confluence 2 that will fail you, 3 will be the lowest you can use…
-
There's a couple of underlying principles in this that Warren handles perfectly and automatically but doesn't explicitly mention 1. REST respects your setup. You need the Resolution to be on the screen so you can set it. An additional wrinkle to that is that any competent JIRA admin will *never* put the Resolution on…
-
The screen layout will be the same - there's only one layout in use. I am assumung that you are talking about the "screens" here, when you say "template", and not field configuration or custom field context. But we will need to talk about them. Here is a list of things you should check: * If you are missing fields from a…
-
I've got this snippet for script-runner. It's a post-function, so it assumes you have the issue to amend as a variable "issue". It also assumes your target field is a text field, as it takes summary as a string. import com.atlassian.jira.issue.Issueimport com.atlassian.jira.issue.ModifiedValueimport…
-
You are not locked to just permissions, you can add a condition on the transition that says "only people in group X" or "only people in role Y"
-
Create a "reviewers" group and put them in it. You can read the membership of groups over REST. Same for JIRA if you're going to talk about projects instead of spaces.
-
Ok, so it's the other reason.
-
Depends on your Service Desk portals. It may make sense to have knowledge bases linked to different portals. But it does depend on how you want to work wiht the portals. You should probably use your existing Confluence - it's probably already got a lot of stuff in it that would make a good basis for KB articles, and…
-
No. JQL is not SQL. A JQL query effectively *is* the "where" clause, it doesn't do anything except give the user a list of issues that match the "where"
-
This behaviour is consistent with a licence problem. Either you've exceeded your licence limit, or your (avaluation) licence has expired.