Comments
-
Just for information, the catalina.out log is a good place to look - that logs what Tomcat is doing, and it's a good place to look for the serious "I cannot start this at all" errors. Atlassian-jira.log only gets written to when Tomcat can load Jira ok and start it. Even if it fails and shuts down shortly after startup,…
-
Actually, there's no real error here. It's just telling you that when you shut it down, a file with a process id was found, but nothing was running with the ID found. IT will have cleaned up and carried on fine. Try restarting it next and see what happens. The most important log file though, is "atlassian-jira.log" in…
-
Because that's the rate recorded since the version began.
-
The velocity is based on the average rate of progress since the version began, not the team completion over an arbitrary period in the past.
-
Because the velocity for the remaining work is the estimate of what goes into the sprint, not how you're currently performing - it's quite rare that they're the same. The scale is not at 100% for the same reason - you might be under or over.
-
Boards do not live "within" a project - they're independent of projects and can include one or many projects. Depends on the filter behind them (project = X is a common one, but you could do "project in (x, y, or z) and issuetype = bug and colour = indigo and and or and or...) Anyone can create an Agile board as long as…
-
No. You need to be an admin to create a project. There's several workarounds - I wrote addons that created projects as part of a "JIRA Project management workflow" (I'd do that with the script runner nowadays) for example. I'd recommend you take a look through the marketplace too - there's at least one addon which directly…
-
In theory, yes, but you're going to have a very hard time of doing it. You'll need a lot of differing code on both ends. If it were two recent JIRA systems, it would be easier because you could write similar code for them. But JIRA 3's remote calls are SOAP and JIRA 6.3 and above use REST only. I also wouldn't recommend…
-
JIRA is a web-application, so you can connect to it from as many places as you like, as long as it is exposed to the internet. I'm not sure what you mean by "automatic update" though. If you're meaning the server version upgrading itself, then no, it doesn't do that.
-
No. Because each plugin could be doing something different. For example, an add-on could * Add a custom field type - you'll want to report on how many issues have a value stored in that type of field (possibly many fields) * Add a report - you need to ask your users who is using the report * Add a workflow post-function -…
-
Simple, you can't. There is a logical reason for this - think about the question "which group"? On one of my sites, I belong to around 45 groups. How do you know which one of these groups is valid? Worst case - *Everyone* is in jira-users on most sites. Basically, there's no logical relationship from issue to users group…
-
If some people can access it and not others, then the permissions and/or restrictions have been changed. You need to ask the page or space owner about it. We have less information on who they might be than you do - it's your system, not ours.
-
Ask the page or space owner if they restricted or deleted it. If it's restricted, ask them to open it back up. If deleted, then ask them where they want you to look for the information instead.
-
Two ways I can think of: 1) I don't know if this one is possible as I've not used Crowd recently, but I think you can separate out the user-directory for the group(s) <> application mapping. This feels messy and I don't like the idea 2) Change the confluence admin groups. By default, Confluence administrators are members…
-
Yes.
-
Yes and no. To see a space, your account must have the right to browse the space. An administrator does NOT get that right automatically as part of their admin rights (Admins can see/do everything is a dreadful design failure), thye have to be granted that right, just like any other user. They DO get the right to see the…
-
Anything you choose to let them do. Check your global permissions and each permission scheme for the use of the "group" called "anyone". If you've got no usage of that group at all, then all an anonymous user can do is get two two screens - login and permission denied.
-
If by "hosted", you mean Atlassian's OnDemand, then no. Only custom "Connect" stuff can be added to that and I don't think that supports the level of customisation you need here. You might need to host this stuff yourself, or find an Atlassian Expert partner firm that does do hosting in a way that lets you install what you…
-
Ok, well, the short answer is that there simply is no way to do this in Jira without a little bit of coding. Issue trackers generally work on the (rather sensible) principle that one person is responsible for an issue at any time and they hand it to other people and/or move it through the workflow as appropriate. If you…
-
This is not clear to me, sorry. Do you mean you want ONE person in that group to say yes/no, or do you mean you want everyone in the group to be forced to have a say before it proceeds?
-
For what it's worth - if you run without Structure to get started, it really is very easy to implement it later if you think you do need it! I'd be strongly tempted to just run with the basics, get that working, and when you have time, put a demo copy of Structure in your test system and see that it solves the requests.…
-
Depends on what you're doing really. I'd always add the Jira Toolkit and the Jira Suite utilities to any installation, plus the charting plugin, but beyond them, I'd be led by what you need from it. Your list implies you're doing software development and testing(Bonfire), including design (Balsamiq and Gliffy). Which is…
-
Depends on what you're doing really. I'd always add the Jira Toolkit and the Jira Suite utilities to any installation, plus the charting plugin, but beyond them, I'd be led by what you need from it. Your list implies you're doing software development and testing(Bonfire), including design (Balsamiq and Gliffy). Which is…
-
Check the field configuration and permissions as well as the screen - the field must not be hidden and you must have "add attachment" permission for it to appear.
-
That's one of the (many) reasons not to try it in javascript and do it the reliable way, in a post-function. For javascript, you're going to need to intercept new page and refresh and update page and other javascript events that update the page.
-
Ah, I see, you want to fill a field with a default value based on other values, allow the user to overwrite it, and have their data over-written if they go back and amend the other values.Definitely possible, but best done in javascript, which isn't my field.
-
I'm not sure I understand this "while created, not as a post function". The create transition has a post-function which is the perfect place to do it - user has put in good data, commited the new issue, perfect time to work out and populate another field. Your script boils down to * get custom field value (impact) * get…
-
Yes. "Screen schemes" let you tell Jira "use screen 1 for create, screen 2 for edit and screen 3 for view". Make sure that the field does not appear on any screens, and the users will not see it on the issues. You'll also need to make sure it is shown in the "field configurations" and it has the right "context" - when in…
-
In addition to the other answers, be very careful with the field. A couple of simple points about it: * JIRA, and many of its add-ons use Resolution as the basic "we need to do something with this issue" / "this issue is done" flag. If you hide resolution and don't set it at all, then your issues are all going to be open…
-
The licencing is tiered, not cumulative. For 60 users, you'll need to buy the 100 user tier. That will allow you quite a lot of leeway in new users.