Comments
-
No, the "create" process can only land in one place, and you can only have one create in the workflow. The closest you can get is to use of the scripting or automation apps that can catch the create during your automated process and trigger an immediate transition to the failed step.
-
I don't believe the SQL macros allow you to run updates. You'll need to write your own code that can.
-
Yes, you can. As your "projects" are represented as issues, and your risks will be too, you can use "issue linking" to link them together. See https://confluence.atlassian.com/jiracoreserver/linking-issues-939937913.html
-
If you don't want Gitlab to update the issue status, yes.
-
Ah, ok, reporting. You should define filters to catch each set of issues you want to report on, and then use those filters in dashboard gadgets. For example, Project = XXX and status changed from fixed to retest And use that in a filter statistics gadget on a dashboard.
-
Many places have teams that work across several projects, especially when projects are built for tracking a product or service, not for a team. As boards do not belong to projects, you often find boards being used by teams to show all their work in one place
-
You can't. Even if you had database access to Cloud (you don't), it's not using MS on the back end so the backup is in the wrong version, and the version of Jira is too different to be able to read your data. To get your current server on to Cloud, you need to upgrade it to 8.1 (remember you must go through 6.4, 7.0 and…
-
It's not an error, it's a warning about potential data loss or required changes as you change the issue type.
-
The most common cause of this error is a misconfigured database. Modify MySQL startup options in the configuration file my.cnf (often named my.ini on Windows), so the transaction level is set to transaction-isolation = READ-COMMITTED.
-
The IDs need to be the ids of any transition you want Gitlab to use.
-
But then you would need to ask the customer which issue type to create, which is something they should not have to worry about. The whole point of requests is to remove complexity like that from the customer. Also, you can't do it - an issue can't be of two different types at the same time.
-
You can upgrade to any version released before the end of your maintenance. 6.14.2 was released on the 3rd March 2019, so you can't upgrade to it without renewing.
-
Calculated fields don't have any "template" for displaying in Edit screens, like editable fields do, so Jira does not render them when the screen is in edit mode.
-
Does the file exist, and does the jira user the system is running as have full read/write access to it?
-
No. You can use a clustered database, but Jira expects to use a connection to a single source, and not have any awareness of the clustering. It just needs one single connection to what appears to be a single database.
-
Um, look at the issue? Sorry, that is a little simple, but you don't tell us anything about what you really are asking. So all we can tell you is that a Jira issue has a status and you can look at the issue (including its history) to track and fetch that data
-
That's an error you usually see during shut-down of the Tomcat. What errors are you getting when you click "update" in the application manager?
-
What are the symptoms of "not able to run"? What does the log file say?
-
Still broken in 8.1
-
Yes, if you can put something into Octopus that can issue a REST call to Jira to trigger the transition.
-
Atlassian can now do this - you need to raise a support call with them with the new name you want
-
Either hg (mercurial) is not installed, or it's not in the environment's PATH for executables. Check that it is installed and the installation is included in the path.
-
Deleting issues is not a administration action, changing permissions is.
-
Project Configurator can do full or partial transfer of config, including workflows.
-
You can now raise a support request with Atlassian and they can change it for you.
-
The most common error is when the Jira system can't talk to itself over the network. Go on to the Jira server and try "wget <Jira base url>" (not localhost, you must use the base url) - if that gives you errors, you need to fix that to get Jira to work.
-
What course and book?
-
As well as the $10 licence, you could let the licence lapse - Jira will continue to work, but you won't be able to upgrade it or get support from Atlassian. Or, with the $10 licence, you could leave it with more than 10 accounts with access, that would make it read-only without permission changes.
-
If you want to default it on-screen, you can use things like the Behaviours module in Scriptrunnner. If you want to set it without asking the user, you can use a post-function in the workflow to set one.
-
The .tar.gz install does not need compiling or building - you expand it and it's ready to run. Where are the "variations" and "mislabeled packages" coming from? Is this a copy of another Jira some previous admin has been messing with?