Comments
-
I cannot work out any way to do this. The mix of multiple fields, text fields, select lists, (potentially) buttons, radio-boxes and all the rest, sounds like a nightmare for the end-user, and even worse for the people who might have to code it. Much as ScriptRunner is helpful, this is not a design it can support. The…
-
Cloud URLs are effectively fixed in place at present. You can ask Atlassian to change them a bit (from xxx.atlassian.net to yyy.atlassian.net for example), but they will not do this frequently, I think it's once a year at the moment. Raise it over at https://support.atlassian.com/contact , but make a good choice of the new…
-
Please raise this as a new question - your comment has nothing to do with this 8-month old question on a separate topic.
-
You should put in the base url of the Jira you have installed, replacing https://<your-instance>/
-
No. Notification schemes work off "events" - these are primarily fired by "changing an issue". Changing a resolution will happen during an "edit" or "transition" event, but may be grouped with other changes. Might well be the only change, but that's not common with resolution (as it should really only happen as part of a…
-
The most common culprit is that the upgrade upgrades the JVM running Jira, which means the client SSL certificate keystore is replaced without a certificate that you applied when you moved to SSL. Yes, I know, that's a lot of jargon and words to throw around. The less jargon-y version is "when you set up SSL, there was a…
-
Customers don't have to create new accounts, an existing Jira account can be used. I understand the voting point, but service desk is not the place to vote for features, it's where you do support. Voting for features is a development project thing, not a help desk function.
-
The update can't run, you have not got to the point where you can write anything to the issue in a validator. You will need to validate first, returning a pass or fail, and then do the update in a post function.
-
Yes, you can't change Cloud urls (well, you can ask Atlassian support to do it for you as long as it's not too often, and hopefully we'll get some more flexibility soon)
-
You really need to cut that permission down to "admins only" - at the moment, the entire world might get access to delete anything they want, and deleting in Jira is very very permanent - you won't get it back. Can you tell us what licence level you have for your Cloud system? And what "type" of project this is?
-
Hmm. Could you try replacing your field name with the customfield id? I.e. "customfield_12345"?
-
Ah, found it. It's always installed on Cloud by default, but Server installs need to add the "Jira Charting plugin" - this is one of 5 I always install so I forget exactly what charts it provides.
-
Created a new one. Have you tried turning off the apps I recommended? This will give you a different error in the log, safe mode is not going to help us here.
-
The workload pie chart is available in Cloud and Server.
-
Ok, as I already said, yes you can use another field to store data, but it is not going to replace the summary. You could, if you have one of the automation or scripting apps, replace the summary with your code, but this is not a nice thing to do to your people - they will put something (useful to them) in the summary, and…
-
It looks to me like Clubhouse does not support status mapping. Unless you've already mapped it elsewhere?
-
And did you apply the fixes for those?
-
That is not a Jira project ID. It's too long and has an invalid character at the start. You'll need to talk to the admins of whatever system this is. If it is a Jira, get them to fix the project key to something valid too.
-
I am afraid this question does not make much sense. Could you explain what you are trying to do with Jira and Confluence?
-
Generally, you don't reindex weekly, it should not be needed on a well-set-up Jira. Have you worked through the steps on the document I gave?
-
This can happen when you've been re-ranking a lot and have used up too many spaces or put a huge distance between some issues. It's more likely to happen when something has gone wrong with ranking somewhere, and you're hitting a broken one. Best bet is to go through the options over at…
-
I would run through https://confluence.atlassian.com/jirakb/gadgets-failing-to-load-in-jira-server-behind-a-proxy-218276785.html just to check that it is SSL related and not one of the other possible causes of that error. You probably should to check over…
-
I think we need to know why you think you need it.
-
Confluence considers pages to be the "folders". It's not a file storage system, it's a wiki, and as such, does not have folders within its existing nested structure.
-
Your "requirement" has changed during the discussion. I've explained that the Summary field type cannot be changed, which was what you originally asked. And I've explained why the requirement is not really of any use. You can add a custom field to hold your extra data, there's no problem with doing that, and I would…
-
Validators should not update fields. A validator is for checking input, and the only thing they do is return a pass or a fail (with an error message, optionally) Do not try to do this. Move the custom field update into a post function, after you know the person has entered something that is valid.
-
What scripting app are you using?
-
No, again, you cannot change the type of the summary field. It is plain text and will always be so. You already have an issue key generated and available in all mails and screens, please don't try to make Jira less useful by putting junk in the summary field, keep it as a short description of why the issue has been raised.
-
I am not sure how you expect a configuration file to disconnect users?
-
I think you have misunderstood. There is no way to change the "type" of the summary field. It is required, your humans find it useful and it has to be filled in. If you want to change that, you will need to rewrite most of Jira (which you can't do on Cloud). You can have other fields for request type and anything else you…