Comments
-
Hang on, that's not what you said earlier - "set automatically on issue creation according to the user's group membership". In the case where you want them to choose, you don't need the script, just stick it on the screen and make it mandatory. Remember that JIRA will only let the user see and select a level that the user…
-
I'm afraid the only three shortcuts available are spaceName, currentDate and spaceKey There might be another way to get something with this though - can you explain what you're trying to do with the name of the page and the "some text"?
-
No, your proxyName is incorrect, you need to use the right server name. A module won't help you get around an incorrect setting.
-
Oh, you want to merge, not create a copy of production. JIRA merges are a different story. Off the shelf, you will need to transfer the configuration for each project manually (there are add-ons available that can automate a lot of it), and then use "project import" to bring in the issues. Note that if you don't transfer…
-
Permissions like that are done on the project level, not issue type. There is a request open to do permissions at issue level, but I don't think it's on the roadmap at the moment. So, while there appears to be no way to do this on the surface, you can actually do it. Obviously, there are add-ons which can help (Behaviours…
-
JIRA doesn't have the concept of a "closed" project, it's up to your administrators to define how you do it. Most of us create a permission scheme that allows only for browse (read only), or no access at all. It sounds like your admins have left the "create" permission open so the project still accepts issues. You should…
-
Most of us take a backup of production and restore it on test. For a small or medium server, a copy of bits of the home directory (attachments and plugins, the rest you don't need or in some cases, want at all) plus the xml export. For larger servers, a standard dump of the database restored into the test database, plus…
-
You'l need to create a temporary 6.2 server, import the data, then upgrade it to 7.2. Data imports from different versions can work as an upgrade, but I wouldn't try 6.2 to 7.anything. Crossing the major release version usually fails spectacularly. (In your case, I'd test importing a 6.2 into a 6.4 install)
-
You'll need to find or write something that can ignore their desire not to be spammed by their own changes. (Note that the global setting is a fall-back - it's used when a user has not actively made the choice by changing their profile) Off the top of my head, ScriptRunner, JETI, JEMH and several other add-ons allow you to…
-
Have you checked that the issues have the properties you're looking at?
-
The "close" permission is a bit of a hangover from JIRA 1 where you could not edit workflows. Check your workflow - what "conditions" do you have on the "close issue" transition? Unless you're using one of the default workflows, it's likely that there are none, so anyone can close an issue. You'll want to add one for "user…
-
Your key is kept in your my.atlassian account, where you can get more keys if you need them. Please note that your question was flagged as spam - I suspect it's because you are using a dubious name in your account, you should correct that.
-
Tempo does something similar to that.
-
Do you get the same problem when you try a simple curl or wget instead of using postman?
-
"Internal server error" is usually impossible to diagnose without reading the logs. You'll need to contact https://support.atlassian.com to find out the details of the error.
-
Not really. There's generally no need for regular re-indexing. I'd take a look at why you're doing this regular indexing and see if it's actually useful.
-
That is the point. You don't. If you set any resolution, you are telling JIRA the issue is resolved. The text you put in there is irrelevant. You need to leave the field empty on unresolved issues. Your "not started" is a resolution, so the issues with it are resolved.
-
Yes it is. Let me put it this way. When you created the "not started" resolution, how did you tell JIRA that this resolution is not a resolution? Answer is that you did not. Because it is a resolution. When you set the resolution field on an issue to anything, the issue is resolved. It doesn't matter if you use the words…
-
To make that useful, you'd have to embed meaningful information in the data and impose complex rules on the naming conventions. It's unneccessarily complex and pretty much pointless. It would be far easier and more useful to implement a scheme that allows you to refer to filters by name as well as ID in the url (There's a…
-
Short answer is that you will get a completely broken index, and you will need to re-index the system in full again. A little more detail: Imagine the process as "throw away the index, then read each issue from the database in turn and build an index record for it". If you shut the service down, it will finish the issue it…
-
That's a very peculiar thing to want to do. Sounds like a totally broken or insane requirement to me, as the Service Desk data is totally dependent on JIRA Core data. Think of it this way - if you exported just SD data, you would get items like * exceeded SLA * a list of request types * some portal definitions But without…
-
Whereever your operating system stores startup information.
-
Check the start-up scripts are ok by checking their settings and try running them to see what they do.
-
That's a job for your network team.
-
It's not just the workflow that matters, you need it to do all the checks and changes. It's a nice idea that you can just have the same status, but that's not the problem, it just means you don't have to do the mapping (and you could easily do the mapping in your code anyway). You will need to dig through the API to find…
-
My instinct would be to look at the proxy server. I had massive problems getting Synchonry to work over https behind an Apache proxy on 6.0. On 6.2+ it works fine if you follow all the docs, but you still do have to fiddle with the proxy setup for it quite a bit.
-
Scriptrunner is a good solution for a lot of things :-) That's why Adaptavist chased Jamie for so long!
-
The most common cause of this is a problem reaching the Synchrony service. Check this by going to Admin -> Collaborative editing, and disabling it. You should find that you can now edit pages, but with the old Confluence 5 style editor. If that happens, then we'll need to look at Synchrony.
-
I must admit I'm stuck on this one - the problem is that the -c option works for me, I get a pile in plain text install questions.
-
Probably the code in the code block - looks like gibberish to spam filters, which raises the score for it. They are looking for ways to teach it better, but it's slow going.