Comments
-
I can't think of a way that Jira would do this without admin changes - someone adding or reconfiguring something that is moving things around automatically.
-
With Jira Cloud, you don't need any of that. You buy the service and it is run for you. If you hook it up to your Active Directory via identity manager, you will need worry about those things, but for your AD servers, not the Atlassian Cloud. If you really mean Jira Server, then see…
-
No, Jira does not have "sub projects". The usual advice is to use "components" (or other custom fields) to divide up a project.
-
Ahh, yes, I do that almost every time as well!
-
It looks like you have pasted the new key into the licence box for Jira Core, not Software. ?Could you try the Jira Software area instead.
-
Ok, * Add target="_blank" as an attribute in your url. * https://library.adaptavist.com * How do you mean "used"? Jira is written in Java (amongst other things). Do you mean writing apps for it?
-
What have you set in the connector in Jira (well, Tomcat) - the server.xml in <jira install>/conf has a line in it that includes "context" - what have you got in the active connector? Also, try dropping the 8080 - one of the reasons for using a proxy is to avoid having to use the port - exposing Jira on just the ip address…
-
I listed a batch of possibilities, I would not expect you to see them all! Escalation for example, probably only there if you have ScriptRunner or an escalation app. I went for these because you show 5 post-functions on the transition, so I doubt there's anything in there, and hence lean towards something doing it…
-
Fields contain different types of data, depending on what they hold, so you need to take account of that when using "getCustomFieldValue(field)". Number fields give you a number, as do estimates. Date and date/time fields give you a date stamp object. Select lists give you "option" objects back, and so-on. You say it's a…
-
It sounds like you have scripts or automation that are detecting your changes of status and deciding to issue more of them somewhere. Check listeners, escalation services, and automations.
-
Then the condition is not based on who the current assignee is. You do need to look at the conditions on the transition to find out why it's not letting you use it.
-
As a Jira or system admin, go to configure the project, click on the workflow section, and change the workflow scheme to your new one. I can't tell you more than that, it really is the process to change the workflow scheme for a project.
-
There is a "condition" on the transition out of postponed that your account is not meeting. As you say "other user postponed it", I would guess it is something like "user who transitioned this issue into the postponed status", but ti could be something else. Check with your admins what the conditions are.
-
As a Jira or system admin, configure the project, click on the workflow section, and change the workflow scheme to your new one. The system will warn you about migrations and ask you questions if it needs to (mostly if your old workflow has status the new one does not, it will need to know what to change existing issues to)
-
The option list is cut off after a certain number to prevent performance issues when there are too many to list fast. If ou start typing a field name, the list will change to list only fields with the letters or part/whole words you type in them. From memory, I think it stops at about 25ish.
-
Workflows are not assigned to projects, they are assigned to workflow schemes. So create a new workflow scheme, and tell it to use your new workflow as the default (or assign different ones for different issue types), then configure the project, changing the workflow scheme to your new one.
-
The changeitem table contains "old value" and "new value". To get the original value on create, read the earliest change of the field.
-
It's the same as it was 6 years ago - add the field to the list of custom fields, give it a default value, then go to the screen you want it on and add it there.
-
These functions are all built into Service Desk off-the-shelf.
-
You have not attached any images of what you are seeing. If you log in, you see a list of systems associated with your account. If you click on any of them, it will show you who the contacts are. I don't understand why you are not doing this.
-
I am sorry that your "English major" has let you down so badly. The fact is that your account has signed up for a service (as you said you did). This service needs to have at least one contact named as the owner and you are it. "Primary billing contact" and "technical contact" are pretty clear to most people - and even if…
-
It's an angrier duplicate of https://community.atlassian.com/t5/Questions/Account-deletion/qaq-p/981739 where I said mostly the same thing, although I think your answer is written more clearly (as usual!) It is a shame that someone lashes out at those trying to help, when the problem is that they are not understanding what…
-
Right, so accepts that you signed up for a system, accepting the terms and conditions, which include having contact details for it. You will need to cancel that, from your my.atlassian.com login, and then you will be able to shut down your account. Could you explain where you are stuck on this? "Nothing makes any sense"…
-
You have signed up for, or been nominated as the owner of one or more accounts. Go to your "my.atlassian.com" account and see what you are named for. You will either have to shut down the systems you own, or transfer them to someone more appropriate.
-
* To add it to the "header", you have to hack the theme so that it shows the page ID. * No. Page IDs are the unique numeric reference in the database. You could, in theory, rewrite Confluence and all the add-ons you might use to have a different scheme, but that would be a massive project and totally unsupportable and…
-
There's not a lot we can do to help you here. Jira does not have any function that will just delete itself. Only the users of the computer can uninstall or delete it. If you need to find out why, you are going to need to ask everyone who has access to that computer. If you have backups, yes, you can re-install. If you…
-
Ok, there is absolutely no way any of us could know that, unless we happened to work for your company. Reasons for upgrading from Jira 6 to 7 are simple * More/better features - 7 does more things you might need, including performance improvements * Support - 6 is well past end of life, so if there is a security issue, bug…
-
Actually, so far, the whole of 7 is compatible on upgrades. So, at the most extreme (for now) you can take a 7.0 system and go straight to 7.13, no intermediates needed at all. Same for 7.3 - it should just go straight to 7.13 perfectly happily. Note, this is from the docs, not experience - so far the largest I've done is…
-
Yes, you are absolutely right. The first and third access method require accounts for the users. The first is a confluence account, the third a jira "customer" account. The second option of "anonymous" opens content up to the world.
-
Probably someone at your organisation who does office logistics. I think you've been directed to your organisation's Confluence (documentation) system, or possibly a Jira (request or issue) system, looked for help, and found a link to here for help. Problem is that this is for help with the system, not help with your…