Comments
-
Notification schemes are for projects, not fields. You will need an add-on to implement something like this.
-
I'd start by reading the Cloud stuff. Everything you can do on Cloud, you can do on Server. The differences are * You need to support the infrastructure underneath the service * You need to do system administration for yourself (making sure it's running, adding plugins, backups, upgrades etc) * Server will always be a…
-
https://answers.atlassian.com/questions/44847/problem-starting-jira-with-atlas-run
-
Ok, that rules out another thought. What does the history of the issue say though?
-
Ok, but what does the issue history say? Specifically, does it mention resolution anywhere? Another possibility - have you got any application links?
-
Hmm. Interesting one. Two more quick things to check. First, could you update the issue in some way - a comment, transition, edit, doesn't matter, just a minor change. Then check how it looks in the stream again. Secondly, look in the history of the issue (post here if possible)
-
Ok, could you run a quick search that includes the issue ( key = "KEO-1" is probably the easiest one to run) I'm looking to see if the result in the issue navigator is struck out as well...
-
Could you go into the issue and look at the "resolution" field? What does that say (if anything)?
-
Yes, you can do this, but you'll need to get another admin to do it, as JIRA requires at least one active admin and won't let you remove yourself.
-
Not natively. JIRA's components are a flat, per-project list. But, have a look at https://marketplace.atlassian.com/plugins/net.brokenbuild.subcomponents/server/overview - I suspect that covers most, if not all, of what you're looking for here.
-
Do your users have "log work" permissions in the project? Is the timetracking field on your screens?
-
In my experience, it's the one that you are most familiar with. My clients have run it fine on all sorts - Ubuntu (with the caveat that I agree with Dennis - OpenJDK is a bit of a pain to run, getting worse, and you'll want to install Oracle's ex-Sun Java to save the hassle), RedHat is extremely popular, as is CentOS.…
-
Bear in mind that this is an *upgrade* not a "restore a backup". You should treat it as an upgrade, and follow the upgrading instructions in the documentation.
-
(Don't feel stupid, the layers of rules in Jira like this one is powerful, flexible and leads to quite a barrage of complex new stuff when you first encounter them. Took me ages to get how roles work when they arrived in 3.6 and I still get screen-schemes wrong almost every time I try to do anything clever with them)
-
The permission scheme is a set of rules that says "grant access to this project to people who match this rule".Most people don't start playing with them until they've messed around with project users a bit first, and I was assuming you haven't either. If that's true, then you have the default scheme which includes a rule…
-
Via project admin - have a look over https://confluence.atlassian.com/display/JIRA/Managing+Project+Role+Membership
-
Go into the project users and remove the "JIRA users" group from the roles. That stops "everyone who can log in can see your project" Now put groups A and C into the users role in project 1, and B (and C? I think you've miskeyed there) into project 2.
-
Go to the marketplace and look for "reports" and narrow it to "Jira" - a lot of the results will be focussed on specific functions which you might find useful, but the first page will include Dataplane and EazyBI. I'm not well placed to recommend one of them over the other, as I'm only a "light" user of both. The main…
-
You haven't set up the connection to Crowd correctly - Confluence isn't allowed to connect to JIRA. Check the Crowd settings (whether embedded or remote). If you're stuck, you'll need to explain more about your setup and user authentication.
-
That's far too wide open a question to answer. We don't know how you're using your wiki, how it's set up, what's enabled/disabled, what you may have customised, and probably most importantly, what you would consider an inconvenience. I think the only way you can get a useful idea is to read the release notes for yourself…
-
You need to write a new field plugin to provide a different layout (you might be able to botch something with javascript or maybe even css, but the correct answer is to have a dedicated field type for it)
-
Duplicate of https://answers.atlassian.com/questions/38835638
-
To explain why: You have made a field called SLA Comments mandatory for the issues, but not put it on the creation screen. Teju's answer is most of the rest of what I'd have typed - although a third fix would be to add the field to the screen.
-
Oh, definitely worth a try. I've just tended to work in environments where SAP is being removed, so I have no knowledge of it. I suspect that if the NetWeaver platform provides a pretty standard java application server, then Confluence will work fine on it.
-
I'd ask sales@atlassian.com, but it sounds more like a SAP question to me.
-
What do you mean by "compatible"?
-
That's what it does already. A user tries to log in, if they get the credentials wrong or the user is disabled, or they have no account, they can't log in.
-
To be clear on that validation option - you're not making it "mandatory on a screen", you're making it "mandatory to go through a transition". It's easy to set up an example where you use the same screen for an "edit" and a "transition", and the field is only mandatory on the transition.
-
Bleugh, can't you just do this properly and use permissions to stop the wrong people creating issues?
-
We can't. We're end-users of Atlassian software and have no access to your system. You really need to ask your administrators or helpdesk, or the person who told you where it was and how to get into it.