Comments
-
Go to https://www.atlassian.com/software/jira/update and have a look at the "older versions" lists and their release dates. You can upgrade your system to any version of Jira released before the 12th July 2019. From memory (and please be aware that I have a terrible memory), I think you're looking at an upper limit of 8.1…
-
If you are doing scrum, your estimates would not be being placed on sub-tasks. Jira is pretty strong on doing estimates and velocity according to scrum principles, and scrum has nothing to say about sub-tasks. In scrum, you tell your PO and others which stories you are going to try to deliver in a sprint. At the end of the…
-
The convert option can only be "removed" by not having the sub-tasks available. If you have sub-tasks available in the project, then people can convert between issue-level issues and sub-tasks.
-
There are two parts to a query - finding what you're looking for and displaying the data about the results. JQL (and the "simple" search) are for the first part. Specifically * issuetype = story and fixversion = "name of fix version" * issuetype = epic and fixversion = "name of fix version" * subtasks are part of issues…
-
You'll have to write scripts that can work out what filters you need and create them. SR canned scripts can't know what you're intending.
-
JSD demos do tend to show you the internal usage, but actually, the system doesn't care whether the people using it are internal or external. There are a lot of JSD portals out there open to the internet and allowing people to sign up as "customers". If you're on server or DC, you'll need to expose the server to the…
-
Yes. Very short and blunt answer, but it's right. A validator only runs when someone goes through a transition in a workflow and all transitions are individual and independent of each other, even within a workflow. So if you put a validator (or condition or post-function) on a transition, it won't have any effect anywhere…
-
Because you want the data that you have a customer. If you don't have an account, you can't report on it and your customer can't have access to their own stuff because you can't know who they are. So you can't eliminate sign up - you don't want to either.
-
Check for Listeners and services. I doubt any service would do this as they run regularly, not by issue change. But listeners can detect issue create/change/anything and be used to do things like creating issues. You'll want to check for other generalised scripting and automation tools like Scriptrunner and Powerscripts…
-
For what it's worth, I made the mistake as well when I first got easked to add resolution to screens. I worked out how to fix it, but needed Neal Applebaum to explain it to me
-
Could you explain "is not working" a bit more? That is a bit of a wide-ranging question, and I can already answer some of it and take a guess at a bit more. The partial answer I have is that putting "order by" in a quick-filter will not do anything. Personally, I would like Atlassian to get rid of the "order by" bit of…
-
Sorry, I spend 99% of my time with Unix-like systems and quote "my.cnf" by habit when MySQL is mentioned. my.ini is for Windows based systems, but the principle is the same (I have a sneaking memory that the files actually contain exactly the same text!). If you change the my config and the database fails to start, you…
-
They're supported. If the database is not starting after you make changes to the my.cnf, then you need to debug that, not look at Jira. I've had the same problem only last week, reading the mysql logs revealed where I'd made mistakes in the my.cnf
-
I cannot tell you what your processes for adding new people are. I'm nothing to do with your organisation, I don't know what you have got set up for user provisioning. Same goes for the rest of us - we have software in common, but most of us don't have any access to or knowledge of your systems.
-
You'll need to ask the space administrators to add people to the spaces, or people/site admins to add them to the right groups.
-
What instructions are you using and what are you doing differently from them?
-
Project settings -> Workflows. Or Admin -> Issues -> Workflows Unless the project is a Next-gen project?
-
You would need to remove all the sub-task issue types from the issue type scheme for the project.
-
You either don't have Jira/Jira-system admin rights, or you're in a Next-gen project, which don't have schemes.
-
Which application? If, for example, you are looking for Jira, the download Jira DC page is a good start - https://www.atlassian.com/software/jira/download/data-center
-
You will need to read the logs to see if it is crashing. As given in the question, I wouldn't expect it to do anything at all - it either does "return true" or ends with no further action - those won't do anything in the UI
-
Yes, but this is clunky, and it will allow people to edit the value. I'd still strongly recommend a scripted field for this.
-
Your script is using a contextual variable. In a post function for example, a script is running as an issue moves through the workflow. It is running in the context of an issue, and that issue object is therefore available to it. The console does not have any context. So calls to issue fail because it doesn't know. Either…
-
Jira Core is effectively a Jira framework. You cannot run Software without it. Core provides stuff like issues, projects, users, app frameworks, workflows, fields, screens, the UI, and and and. Software has to run on that platform to be of any use, as Software doesn't have most of that itself. However. This is quite well…
-
The parameters that are requested in the Jira document are required for a stable safe running version of Jira. If you're making changes to the my.cnf and those prevent the database service from starting, then you need to debug the database service, not Jira. You'll need to read the database logs to find out why it is not…
-
Where is your script being run? I ask because the "issue" object is only directly available when you are working in the context of an issue. For example, if your script is a workflow element (post function, condition, validator, etc) or it is a scripted field, then the code is run with the variable "issue" holding the…
-
Grant "transition issue" permission to the Reporter. You may need to grant other permissions if you have conditions on your workflows, but those will be down to each condition to check.
-
You get the licence message from the SDK because it uses "time bombs" to prevent you trying to use it as a production system. You can ignore it in the SDK built test rigs. Also, it's very unlikely that your SDK kit is running the same database type as production. I've just answered your question about deploying apps. If…
-
When you build a plugin ready to be spun up in a test environment, the build creates a plugin object, usually a .jar file, sometimes a .obr. You can add those to your production system via "manage apps -> upload"
-
That depends on what gadget you are using to display the tasks, as that determines how it is thinking something is complete or not. Could you give us the title of the gadget you are using to start with?