Comments
-
The screen has nothing to do with the event being fired. You just need to look at the current assignee and their availability.
-
Cloud does not allow you to use user macros (they can be dangerous and hard to support), so it's not one of those you need to look at. We'll need more information about this "macro with page properties" - a screenshot would probably tell us everything we need to know, but a description of content and location might be…
-
Ok, can you explain "not able to edit" please? What are the exact symptoms?
-
Have you (as a project admin) added any components to the project yet?
-
You could do that, which would force the team to deal with the new issue But, it won't be estimated, so you'll have no way to plan for that to happen. Or, if you do increase the estimate, then your scope will change for the sprint, which also makes it much harder to plan reliably. If you're going to bring things into a…
-
We didn't see much Jira in the keynotes. There was a lot of Trello though, could that be it?
-
If your bugs are never making it into sprints because of other work, that implies your backlog is growing faster than you can deal with it, which usually means your team is under-resourced. You need more people to deal with the incoming work.
-
No, again, you can allow your project admins some edit actions in Jira 7.3+ Please try that. Global admins get everything.
-
Yes, that's right for Cloud, although there should be a create link if you're on Kanban. Which presentation was it you saw?
-
Boards don't really "belong" to projects. It sounds like you've made a change to a board which might mean the board no longer fits the criteria for being the default board a project might show to users, but you should be able to just select the board again from the drop-down on the left at the top of the panel.
-
Indeed, think of boards as views, not containers. If an issue is on a board, it is because the board has selected it for view. It doesn't "belong to another board", it's there because the current board is configured to include it.
-
You've been able to do that for a very long time. Jira Software provides scrum and kanban boards, and if your administrators set up "simplified workflow" for a board, then board admins can add and remove status (they've always been able to change columns) Cloud Jira Core also has a business board which keeps a simple…
-
My answer described "administrators for a project". Global Jira admin gives access to all projects, and should only be granted to a small handful of users who work closely together, or you will get into a right mess.
-
Could you give more detail? What exactly are you doing and what happens when you save? Do your logs have any errors?
-
If you have Jira Software, you can allow editing of the workflow to project admins by using "simplified workflow" on a board. Otherwise, not until Jira 7.3, where a project admin gets some access to the workflow as long as it's workflow for their project only. 7.4 then adds some stuff about field values. But you need to be…
-
Does not matter, as long as the schema your Jira uses is isolated from other databases.
-
You can continue to use the existing database and simply upgrade it. You will need to go through Jira 6.4, and 7.0 before upgrading to the latest one though.
-
What does the catalina.out log say at the time everything stops?
-
You can generate a trial licence in your my.atlassian.com account, we can't generate them for you.
-
There's a request open for that with Atlassian, but they've not implemented it yet.
-
You definitely want Confluence. For workflows, you have a couple of options. Jira is a powerful issue tracker with a lot of features, and has fields and workflows as its core function. However, it is over-kill for a lot of cases, especially if your output is purely going to be confluence things. I'd consider a look at…
-
Ahh, excellent. The "log into another atlassian site" trick is one that has been working more and more since Atlassian started moving people over to Atlassian accounts for everything.
-
It's generally better to let all new stuff go into the backlog, as that keeps your sprint reporting clean. Scope change for existing sprints is a pain and makes it hard to see what is happening, which makes your planning harder. If you find you need to be drawing things into sprints a lot because of various pressures,…
-
No, that's correct. You had not mentioned "by issue type" before.
-
Atlassian applications do not run on IIS. You install and run them independently, and they use their own application servers bundled with the installs. Once you have them working, you often want to put them behind a proxy web server, so you can change ports and/or run them on specific urls that suit your organisation's…
-
You need to get them into the far right hand column of your board, and then close the sprint. Boards and sprints do not use the resolution at all, and only really use status to determine which column an issue is in. What matters to them is the right-hand column.
-
Yes, the permission scheme applies throughout. Look in the permission scheme for "can be assigned issues" and set it to say "Role: X"
-
If you are on Cloud, there is an "impersonate user" feature in user management section. If you are on Server, you'll need to install one of the add-ons that provides "su" functions. (I know ScriptRunner does it, and there's at least one add-on for doing only "su" in the marketplace. I have a feeling there are several that…
-
Ah, right. You are doing everything correctly. So, does that email address have an Atlassian account already? If it does, then are you entering the correct password for it? Could you try going to another Atlassian site (my.atlassian.com for example) and making sure you're logged in there and then refresh the page in the…
-
Or using anonymous access?