Comments
-
"It doesn't work" does not tell us what the problem is. What errors and messages are you getting?
-
That tells us the database is damaged. But not really why.
-
Create sub-tasks under the parent. The first one you'll need to create from the actions menu, but once you have one, a panel will appear showing them, and that has an "add subtask" button on it. Your administrators will need to make sure you have sub-task types in the project's issue type scheme.
-
Ah, so you renamed Epic and broke it.
-
It looks like the whole of Thursday has been deleted, along with Wednesday and some stuff up to mid-day (BST) today My profile at 14:00 BST Friday says:
-
Hmm. That suggests a duplicate entry in the database has got in somehow. If you go to the default issue type scheme, does it show the duplicate? If it does, can you remove one of them and see if that fixes it?
-
Remove the extra issue type from Admin -> Issues -> Issue types
-
Server or Cloud? If it's server, what do the logs say? If it's Cloud, then raise it with https://support.atlassian.com/contact
-
Jira 4 supports basic (username/password) only, from memory. Without add-ons, anyway. You should upgrade it to a secure and supported version, then you'll be able to use Oauth.
-
Duplicate of https://community.atlassian.com/t5/Jira-discussions/How-to-connect-database/m-p/644354
-
In more recent versions, it's called "Search template"
-
You'll need a bit of code to put in a post-function to set the security level automatically.
-
Defintely need to read the logs. Check the time you tried to do the save of the diagram, and then the time you tried to read the page for it.
-
So, you exported from the H2 backed system, then tried to flip it to PostGres? Did you clean out the home directory first?
-
Ok, that's a start up running ok with warnings, but no shut-down information. That suggests either some serious internal fault, or something in the OS is killing it very hard, not giving it a chance to shut down cleanly. It's hard to diagnose what that might be, as there's no logs. Do the application logs say anything, or…
-
Moving an issue tries to retain as much of the issue as the target project allows for, and as Sprint is a global field, it's not going to clear it. You are right you can do it with ScriptRunner - a listener could be scripted to catch "issue moved", check you want to lose the sprint and clear it (and other fields) by…
-
It's not that simple - boards are only associated with projects by their inclusion in the board filter. And a filter can say "project in (ABC, DEF, XYZ), so you'd have to handle multiple projects. What is your script trying to achieve for the users?
-
The Backbone one doesn't have to - you don't have to have identical processes on both sides, or even sync in both ways.
-
To show an issue in a board, it has to exist in the Jira system the board is in. So, you need some form of copy of the issue in your system. Best option would be to set up a synchronisation between the two systems. Have a look at the Backbone and Exalate add-ons in the marketplace.
-
I rarely see Epics assigned to people, and even when they are, it's more about ownership than action. Stories are where assignee really matters to most of us, as it's "which single person is currently responsible for this?". For sub-tasks, yes, we assign - one of the reasons for using sub-tasks is to split up a story so…
-
I don't understand? If you can hit a REST url, you can fetch an http one the same way. The data you get from REST is just as "accurate" as what you get from CSV or xml links, it's just a different format (although I'd say JSON and xml are better representations than xml)
-
Unfortunately, they don't do community licences for Cloud, which would give you an instance to play with :-(
-
Ah, you have "fielditis" and you are in need of your admins simplifying your system back to something useful! The only way to fix this for a standard user is to reset the filter layout to the default. That includes the standard Status, so you can then add your other fields back to it. (This is hoping your administrators…
-
Yes, just hit the url the issue navigator links to for an xml or csv export.
-
See also https://community.atlassian.com/t5/Jira-questions/How-to-access-JIRA-with-a-community-server-license/qaq-p/643428
-
A scripted field is aware of the issue it is running for. You don't need to think about it, you can just use the issue object like my code does. The customField is worked out by the line above it in the script. The "see item" is some text I added as an anchor for the url field, so you see something like "See item: 12345"…
-
I don't know, I've not used PowerShell since I gave up on Window many many years ago. The xml and csv should still work though, they come over plain http(s) with no formatting.
-
Ok, you're going about "anonymising" it in a broken way. You should never delete this stuff, just change it so it's not identifiable. Please, step away from the database, you could be doing all sorts of damage by doing things you don't understand. For anonymisation, do it the correct way - see…
-
Probably better asked of Atlassian for an answer than the Community. Https://support.atlassian.com/contact will get you an official answer (we'd ask you to share it here, for info)
-
No, it's JSON only. One of the reasons REST throws out JSON is that CSV is generally too simple to represent some of the data usefully. I suspect the problem you're having "flattening JSON" is because the data simply doesn't fit into a CSV layout. However, you don't have to use REST - you could also hit the urls in the…