Comments
-
There is no 6.8 Jira, but whatever you do have, the process is * Upgrade it to 6.4 * Upgrade to 7.0 * Upgrade to 7.10.x * Export to xml * Build the configuration for the projects you want to import by hand in the target system * You can now use "project import" to pull in the issue data in from the xml export 5 is a manual…
-
If you have no "delete" option there, you will need to ask your space admins to grant you the permissions.
-
I'd guess that you're mistaking "issue is assigned to me" with "sub-task is assigned to me", and your sub-tasks are not assigned to you.
-
How are you "pulling the test cases into this test set"? How are you "pulling the test set into a test plan"? What is a "Test execution"? All of those things very strongly suggest you are using a testing add-on (or possibly Structure) I can't begin to help without knowing which one it is.
-
Good question, definitely looks like a bug to me. You definitely have an bug here, but it would be useful to confirm exactly where. Could you give us a screenshot? Feel free to obscure your data (names, your urls, and definitely SEN or licence details) - it's the location when you see it that I'm looking for. Or, better,…
-
The plan should be * book downtime with users * stop Jira * take a database export * make sure you can restore that somewhere else * run the SQL * restart Jira and run a re-index (if you're on 6.4, then the re-index no longer needs to be the full one, a background will do) But, this is still one of the few times I'm happy…
-
You appear to be getting a GC log, which implies a memory error. Have a look also at the <confluence install>/log/catalina.out file for memory faults.
-
Yes, if you log into the domain admin settings with an account that has the right to add one.
-
Not directly in the UI, so if you're on Cloud or don't want to risk potentially fatal actions, you have to do it manually. But, this is one of the few times I'm happy suggesting database access on a Server system. See https://confluence.atlassian.com/jirakb/changing-custom-field-types-in-jira-158357.html for that (and the…
-
Ah, ok, I can't help you then. I need to see the errors in the logs, but on Cloud, we end-users can't get them. I am sorry, but this will need to go to https://support.atlassian.com/contact Note that if this redirects you back to the community, then you have a "starter" licence which means only community support. If that…
-
If you're calling a bash script, then the call to it is some form of "exec" statement, in which you can include parameters. Let's say you had a bash script that simply said echo $1 Then the code calling it in your post-function can say something like exec ("/data/scripts/myjirascript.sh " + issue.getSummary() ) and you'll…
-
Again, if a person can use the system, they can use the gui and REST api.
-
When you're writing a post-function script, you have direct access to the issue without having to do anything. The object issue is passed into the script for you to work with directly, so you can do things like issue.getSummary() without importing anything.
-
My guess is you've been reading documentation for Jira Server and not Cloud. The two have very different front-ends now, and although a lot of the underlying principles are the same, they're different products. With most of the docs you've been reading, look to the top right and make sure the "cloud" button is selected.
-
I suspect the application log is the one that will trap this error. It should be in <confluence home>/logs/ and the main one is atlassian-confluence.log You can work out <confluence home> from the system information page.
-
Probably https://developer.atlassian.com/server/jira/platform/getting-started/ if you can't find anything in https://marketplace.atlassian.com
-
You'll need to talk to the administrators of the system then, as they've configured something to put this restriction in place.
-
Does the log file say what the system is doing?
-
For Cloud there are a couple of Apps that allow some customisation of email. See https://marketplace.atlassian.com/search?hosting=cloud&product=jira&query=email
-
Yeah, sometimes they're getting padded with control characters - the %A type thing. Removing them from the end fixes it.
-
Apps are installed globally. Some have code that allows them to be used in only some projects, but that is up to the App, and it still needs to be installed and licenced globally.
-
Is this in a Service Desk project, where you have constrained working hours?
-
Log in as an admin, go to the project and find the project settings. They include the workflow(s) in use, which you can then edit. Evaluations of Atlassian stuff are fully functional, just time limited.
-
Ok, so it's from multiple tab use. That makes sense. I'm afraid until they fix it, you'll need to stick to creating issues in the same project when you have multiple tabs open.
-
No problem, when it's text, I can get by with google translate! I am sorry but the error is one that does not tell us much. What you'll need to do is go to the logs and read them for the underlying error.
-
The diagram you've shown is not a simplified workflow - the arrows between status have been added. However, could you hover over each of the arrows coming from the "all" boxes as well. One of them will be called "selected for development"
-
Hmm, ok, so it works in staging, but not production. That definitely needs to be something fixed on production, but I can't think of a way to hide the field like that.
-
These are all parts of other systems, and those systems will install them if needed.
-
Almost every add-on works in a different way and has different routes by which you might measure "usage". A post-function for example, is used when a user pushes an issue through it in the workflow. A report needs them to click on the report. A custom field is used every time an issue is changed or viewed, or a search run…
-
That is in the configuration of your system - your admins have made the owner field mandatory.