Comments
-
So, that's a human failure, rather than the software. There's a better way to fix it - find/write a listener to catch "issue assigned" and transition the issue if appropriate.
-
It's the login for the user you wish to execute the action. For example, I am usually email, name, login: nicb@somewhere.com, Nic Brough, nic You need the login for this.
-
For SQL inserts: * Take your Jira service down. * Take a full backup of the database with your database tools. * Restore this on a test system to ensure it is valid. * Run the SQL to hit the 4-8 tables you need to amend/insert into * Restart Jira * Re-index it * Test every area of user interaction works for an old user and…
-
I assume your priorities are done with the system field called "priority"? This is a field that has a sort order defined by the admin, not by the content, so your order by clause will be working off that sort order, not 1, 2, 3, 4, 5 (although, as an admin, I would be setting that sort order) Can you check that it is the…
-
You have a custom field called LOB which your admins have not placed on the create screen for defects. They either need to add the field, or change the field configuration to make it optional in there. You might find the "where's my field" helper useful, it's at the top right of the create screen.
-
No. The email needs to be unique. For historical reasons it is possible to have atlassian accounts with the same email address, if they've been inherited from the old system, but one of them will effectively mask any duplicates.
-
No. Two reasons: 1. Cloud does not yet allow you to change the base url for a Cloud system - the only way to do it is a replacement - "buy a new one, export from the old one and import into new" 2. Cloud does not yet support anything outside the Cloud domain. The url must end with .atlassian.net Both of these are things…
-
You can export a space from the space tools. If you're on Cloud, the version is not of that much use directly, you simply consider it to be "the very latest"
-
Errors will be in the application log, atlassian-jira.log, but they won't help much, you need to get a new one from the vendor, one that is compatible.
-
Only if you get the configuration wrong.
-
Or you could remove the redundant one you've added and use the permissions to control who can assign and be assigned.
-
Incompatible add-ons can often be loaded into a system, but they're flagged incompatible for a reason - they usually don't work. There's no "fix" for this, you need to get a new one from the vendor, one that is compatible.
-
You need to open up the access from "private cloud" to the device your mobile application is running on. Most of us would either make the "private cloud" public (but secured) or create a VPN
-
There is not enough information here to help you a lot, so we need some more questions. Let us start with "I got a warning that the database needed to be update." Jira does not do that. Could you explain what you saw, what it suggested you should do and what route you then took?
-
Hmm, that's a change of policy, they used to let you change the number. Thanks for the update!
-
Yes, workflow transitions have "properties", one of which you can add is "opsbar.sequence". When drawing up the workflow options, Jira adds them to the list in low-to-high order. (Where it has no sequence, it uses the transition id) If you're going to use this (and I would), then give yourself some gaps - use numbers like…
-
Nearly right: 1. Yes - but specifically, Jira Agile gets converted into the application "Jira Software". So you're moving from Jira + Agile add-on to Jira + Software Application 2. No, there's no conversion! A key for Jira Software will activate an older Jira Agile add-on, and an Agile key will work for Jira Software.
-
On Cloud, you can raise a support request at https://support.atlassian.com/contact and ask them to change the default number of items to keep on screen. If they set it to (say) 5, then up to 5 workflow actions will show before 6 and above get shoved into the "workflow" drop-down.
-
The posts I found all boil down to people having added their own assign options in some way or another, usually in the workflow.
-
That doesn't really help, it just suggests the filters are not doing what you think. Could you give us the board filter and the two quick filters as I asked before?
-
If you want good integrations with Jira without having to think, and/or don't want a new server + software, I'd reach for Insight, a rather excellent Jira add-on for managing assets.
-
All Atlassian products are licensed in Tiers, but that's not really what I was talking about. All your users are effectively using the add-on product, even if they're not using its front-end.
-
That's how I'm reading it. The development docs suggest this is the way to do it as well. Without explicitly saying it.
-
Good plan. I'd also think about doing that on the dashboard with the "introduction gadget" if you don't want an omnipresent banner!
-
The Jira interface is a lot more complex than "a bit of html", rebuilding the dashboard is not a simple task. Your best bet is to design a system dashboard that works for your customers, not start messing with the internals.
-
The button should appear for anyone with Administer projects. Are you 100% sure it's the right person and the permission scheme is correctly associated with the project? (There's three "nic"s in our tracker, hilarity ensues when they pick the wrong one of me...)
-
Comfortably, 300ish. Beyond that you'll start finding it frustrating. Humans struggle with 300 in a backlog, let alone the computers. I'd look at splitting this backlog up - do you have some easy criteria you could use to divide the list up into manageable chunks? At least temporarily.
-
Look at the project's permission scheme. There is a permission rule in there that says "these people can have issues assigned to them". The user you are trying to assign to does not match that rule.
-
As Trello is a web based service... no.
-
AWS is a container that will be running Windows or Linux for you. You'll need to log into it and get to the Jira installation, so you can download the versions you'll need and run them on the server so they do the upgrades. Backups and testing are your friend here.