Comments
-
It will do, if you've failed log in too many times. You need to repeat the process Suren pointed to to reset it, but also fix the directory so it tries to read a valid one.
-
Release simply stamps the issues with a version, so that the board "sub-filter" drops them from the board. It won't affect anything else, the issues don't change in other ways.
-
I have no idea, it depends on what you've customised and how.
-
That on/off is for a bit of a change to the issue view. Not the whole "new" UI structure, I'm afraid.
-
What "type" field? If you mean "issue type", look at, and amend, the project's "issue type scheme" If you just have a "Type" field, then that is a custom field, and you need to go to Admin -> custom field -> "Type" -> Configure, where you can amened the list. I suspect you mean the first though.
-
You don't have the workflow in "edit" mode, look for the edit button, then you'll find add is not greyed out.
-
That does not do anything with project permissions unless your permission scheme explicitly says it will.
-
Correct. Project administrators can only make modifications that are unlikely to need Admin understanding of what they do. It's very easy to break everything with some workflow functions, so those are limited to Admins.
-
I'm not sure you can squeeze all the required validation code into a script, they're limited in length.
-
Unless you've relocated them, <jira home>/logs/atlassian-jira.log is the first one to look at.
-
Correct, it's not needed because they're separate.
-
Is the email arriving in the in-box? If it is, then Jira will be trying to import them, and you will find a reason for it failing inthe logs.
-
The only way I can think of doing that by using accounts with different privileges, or hacks that edit your menu.
-
No, you've not understood what it is doing. Developers see three columns, effectively to-do, in-progress and done. There's no extra status or manual transitions, you don't need them. Developers sprint as normal. The quirk in what I've done there is because I have over-simplified, and assumed that testers will not pick up…
-
It's feasible, but horrible, as you're constantly working to plaster over cracks and writing history that you don't need or want instead of preventing the data going wrong. But, as you say, Cloud doesn't support it at all, so your only option is to fix your workflows and screens.
-
Sorry, I'm behind as well! The email address is the one you want to use for the login, presumably the same as your own system. The "external projects" are shown in the other system.
-
Issue type is a structural thing, and changing it is not trivial. It can only be done easily if the old and new issue types are configured identically. I'd question the desire to change the issue type as a matter of course. It suggests a broken process rather than a useful step. Are your users routinely raising the wrong…
-
There's no way you can reset the password yourself if you can't get the email. You'll need to contact Atlassian support to get ownership of the Bitbucket account moved to someone else. Raise it at https://support.atlassian.com/contact
-
You probably don't. The desire to move an issue as part of a process flow indicates that either your process is wrong, or more likely, you've not set Jira up to match your process correctly. Moving issues is an exception, it's mainly for "I created this in the wrong place" and "we are re-organising Jira". It's a complex…
-
That's the content list of a custom field. There is an issue export, but not an option list export. That said, it's not too hard - go to custom fields, find "type" and configure it - you can then scrape the list of options out of the browser. Not ideal, but a lot quicker than writing them all down.
-
ScriptRunner is the one I would use, because it lets me write a listener that can do anything.
-
I'd agree with the principle. The done/not-done flag should be based on a meta-status (with a flexible relative modifier for reporting), and the resolution field used only to describe the reason for closure. Then we wouldn't have to do anything in the workflow. That should have been done in Jira 2, when we were given the…
-
The import trick in that page is using issue import to create the options list. You have to create issues in order to perform the trick (you can always do this in a junk project and delete them later). When you create issues via CSV in Jira, you MUST give it a summary.
-
The customfield_xxxxx format is hardcoded as a standard throughout Jira and its add-ons and applications. Unless you fancy rewriting the entire thing, Krisz is spot on.
-
What you're trying to do is fundamentally broken here. You say "I want a continuous solution that resets the resolution whenever the ticket isn't in a resolved state." The way an issue gets into an incorrect state is through a broken workflow or screen definition. You should fix all the workflows and screens that allow…
-
You can define whatever fields you want for Jira issues - that's what custom fields are for. For a list of the built-in "system" fields, see Richard's link below - there's a table part way down with a line "fields" that expands to show the system fields that are always there (but can be ignored or hidden if you want)
-
Absolutely, JSD is built for this. Almost. The negative bit here is that Jira Service Desk does not have any off-the-shelf 'phone logging built into it. The range of possible systems and what you might do with them is far too fragmented for Atlassian to build anything in. They ask people to write add-ons that extend JSD to…
-
It was finally brought in line with the others when Charlie was killed off, and all the icons and branding revamped. R.I.P. Charlie
-
Ok, you'll need to look in the logs to see what both sides think is happening, as either Jira is not getting the right data, or Confluence is not sending it.
-
You need to tell Jira that it is going to be used as a directory by Confluence, and set up the access name and password for that, then use the same details in Confluence.