Comments
-
Although, as Charlie was "put to sleep" in the rebranding, Scott finally admitted the logo was horribly wrong Atlassian called their mascot Charlie rather than Atlas, so in the first four images in @Daniel Eads posts, it is Charlie holding something up, not Atlas. But, the imagery is wrong. Atlas was a Titan who held the…
-
Mmm, that is very risky, and not supported! I've seen places have problems when they don't do the recommended upgrade from 6.4 to 7.0, and these can linger, not appearing until later cycles. The one that springs to mind was that when priority schemes were added, they cannot be enabled unless the data had gone through the…
-
An issue is "done" when it is in the last column on the right hand side of a board. If it's not in that column, then it will appear in the backlog, because it is not "done".
-
Don't estimate on sub-tasks if you're doing Scrum, it won't work.
-
Usually, a desire for "templates" in Jira means you've got a set of fields you don't actually need. Which is why there's no templating system built in. And you absolutely do not want "pre populated text" in text fields - you can guarantee you will end up with piles of issues with just that text in there and nothing of any…
-
Ok, so the question is what did you change (probably in Jira, as you've tried different clients)? And what are the authentication errors you get? They might help you locate what changed.
-
Change the base url in admin -> general configuration.
-
Ok, there's no post-function, so you must have a listener or automation doing it. And it must have been coded to only act for that certain user. It's either that, or the user has something external that is creating the extra issue.
-
Project is not a "field", so you can't just edit it. It's a container for issues, which is why you have to use "move" to move the issues from one project to another.
-
Have a look at https://library.adaptavist.com/entity/create-a-subtask-and-link-to-parent-issue-in-jira - you can probably drop all the "link to parent" - you don't really need it, as there is an inferred link anyway.
-
The "jira" user is used when an external system has made alterations that have then cascaded down into Jira. This is because your site admins don't necessarily have to be Jira users, they could be maintaining users without any access to Jira.
-
You should not have accounts with invalid email addresses. You'll need to set them to have proper email accounts, or they are useless to you.
-
Also, if you do add another "done" type column, it won't be classed as "done" unless it is the last column on the right-hand side. Jira only looks at the very last column on the board to define "done".
-
It sounds like the issue is in a status which does not have a transition with id 6 out of it. The comment won't apply because there's no screen for the transition for it (because there's no transition)
-
Yes, you need to let it run the full export. If you think it's failing, you'll need to read the application log to find out what is going wrong.
-
It looks at the issue history and compares it with the sprint. Issues removed from sprint applies when a sprint is in progress, an issue is included in it, and you do something that removes it (e.g. go into the issue and blank out or change the sprint, or drag it out from the backlog, or make a change to it that drops it…
-
Specifically, install an empty Jira 6.3 and restore the backup into it. Then upgrade that to 6.4, then 7.0, then 7.12
-
"Adding a custom field" means creating it and making it available to projects. If you configure it to be available to old projects, then the field is there, you're done. You may need to reconfigure screens as Daniel says to make it appear as well, but that's all.
-
Probably start with https://confluence.atlassian.com/jiracoreserver/getting-started-with-jira-core-938846183.html
-
Why did we ask you? Probably you're using one or more Atlassian product and this is a community of users to engage with Purpose? Mainly help, but we're also here to be sociable (check out the non-technical discussions) How we do it? We talk
-
It needs all of that 768M intermittently. The most obvious time is during start-up, but it's going to need it again during normal execution. It doesn't matter what memory it is using now, it matters when it peaks, which it will do. With too little memory, it's always going to be painfully slow, but it's going to crash a…
-
Ok. It's almost (but not completely) impossible to not have a System Administrator account. But that does not necessarily mean you have the login for it or even know which account it might be! https://confluence.atlassian.com/doc/restore-passwords-to-recover-admin-user-rights-158390.html covers it though, giving you a…
-
You can't. The memory check has been coded into Jira because it really does need it. Even if you do manage to bypass it and drop it to 512m, you'll find Jira rarely gets through the start up process without timing out or running out of memory (and there's no chance if you've got JSD or Software or any of the bigger Apps…
-
You have a post-function, listener or automation that is creating new issues when your old issue is closed. I'm afraid we can't tell you a lot more than that. You will need an admin to find that, explain why it was set up, and talk to about modifying the behaviour if it's not to your needs.
-
The project is given by the key of the issues in the right hand column!
-
This is because it was flagged for release in 7.11.3 by the developers originally, but they moved on to 7.12 instead.
-
You'd want a bit of coding or automation that would look at values set and set a "level" automatically. Bear in mind that you would also want to avoid setting a level a user cannot see, as that looks really odd.
-
It is what security levels are for - the "level" field is a simple drop-down. You set it to a value, and that value tells you who can see the issue (they still need project rights too - but it narrows it down to issue level)
-
It's covered by https://confluence.atlassian.com/doc/migrating-to-another-database-148867.html (that doc has barely changed since version 4)
-
No problem. It is well buried, and not easy to find in my opinion!