Comments
-
Boards do not belong to projects, that drop-down just works out if there are any issues from the project on a board at the time you use it. For the missing board, what is the filter?
-
Indeed - see https://community.developer.atlassian.com/t/jira-server-customers-are-temporarily-unable-to-download-apps-in-upm/9247 as well.
-
Is this in the body of the pages, or is it popping up a warning? Could you give us a screenshot of it in place in the page (not just the warning, but some of the content around it)
-
SQL is the single worst way to get any information out of an Atlassian application. Calculated fields are not held in the database at all. So you can't get them with SQL, you need to duplicate all the logic behind them. I'd suggest thinking of a sane way to do your reporting, rather than digging in the database.
-
Go to "manage applications" and try enabling Jira Software (Jira Agile is not available for Jira 7.0+)
-
Excellent. I am sorry that I neglected to mention a backup of the default, that is a very very good idea. I've installed so many, I don't know if I'm just over-confident in finding/creating a default for comparison, or I've just unwittingly memorised the defaults.
-
You'd need to hack all the project templates so that they selected a different scheme. But, you can just edit the default scheme so that it's right for you.
-
It's more a case of Lotus not having a usable export format, but yes, it's going to be a lot of work to do this.
-
It's my bedtime, so I can't follow this up urgently, but I would: * Check the logs for a reason for the failure * If there's nothing blindingly obvious that makes you say "oh, I can see how to fix that" immediately, raise it with https://productsupport.adaptavist.com/servicedesk/customer/user/login?destination=portals…
-
Your add-on licence needs to match the tier of your data centre install, same as Server. If you've got 1,000 DC users, your add-ons must be licenced at 1,000 users too. 1,000 users with 200k issues is not usually big enough to look at DC in most cases, you have a way to go before I'd worry about it. DC and the add-ons are…
-
I think, but have not tried, writing a scripted custom listener, although I don't think I'd use JQL. It could catch the "create" event, check the rules and then set the "epic link" field to the right Epic. (I think the original question was about moving issues, which I'd never attempt to write myself!)
-
You need to create a dashboard for yourself, before you can add anything to it it (option is under "manage dashboards"). Once added, you'll see the add-gadget option to the top right.
-
You usually need to add the "time tracking" field to the screens for sub-tasks. But if you're planning to use the estimates in Scrum boards as the estimation basis, then, um, don't. Until you've thought about it *very* carefully. It doesn't work the way you think it will, and you will end up with boards that make no sense.
-
That's exactly what the support values are for - telling you the versions it works for. You can try installing an unsupported version, it might work. It probably will not, and it could stop your system working at all.
-
That's exactly what the support values are for - telling you the versions it works for. You may be being confused by the EAP - that means "early access", and generally doesn't get shown on the marketplace because it's not suitable for production, so most people don't care about those versions.
-
You'll need to read the confluence and tomcat logs to find out what is going wrong. (Atlassian-confluence.log in <confluence-data>/logs and catalina.out in <confluence-install>/log)
-
It depends on what you mean by "state". You could have that as a resolution option (so when a user closes an issue, they select "resolved by user" as the reason they're closing it) You could build it into your workflows as an end status as well. Or do you mean something else?
-
That is not related to this question. For better visibility, try asking it as a new question. (However, this usually means a badly configured workflow function, probably a validator)
-
Ah, great, thanks for the update!
-
I'm sorry, I've made a horrible mistake. In your previous comment, you said you had set jira-home. You need to set jira.home
-
I'm not sure. Is that in a Service Desk report or in plain Jira? What's the column header and the report title?
-
That doesn't sound too right - could you check the permissions on the files in your Confluence install? Also, check that you have the global permission "browse users"
-
Not without hideous hacks and checking with your governance people. Deleting users in Jira is not recommended, it makes an interesting mess in your history. Flipping comment authors over to another user is a really bad idea too, as it destroys the information about who made the comment (that easily becomes a compliance…
-
Indeed, yes, they're all "IT change requests", and yes, I'd make the "component" field mandatory so that your users have to fill in at least one (and hopefully get it right). I'd probably set up the components with leads, and aim to choose leads who are going to be the main approvers, then a little education on "if it's…
-
Yes, but the layers in Jira won't support you in the way you describe directly. You've got sub-task, issue and project as the main artefacts, and you can categorise projects as a very simple layer above them. Then there's Epics (if you have Software) that layer themselves across project. Then if you get Portfolio, you'll…
-
Could you check what the end of the catalina.out and atlassian-confluence.log files say?
-
Sprints do not belong to projects, they belong to boards. You therefore need a way to include issues from other places. You could do "project in (Y, M)", but that will get everything in both projects. The most simple option is a bit of a cheat. On the board sprint X belongs to, change the board filter fro "Project = Y" to…
-
Either types or components, or even a custom field would do it. I would ask a slightly different question - are these things going to behave in the same way within the project? If they're identical, then keep it simple and use a simple "approval" issue type, and components or a custom field. If you need different…
-
On the parent issues, you can toggle the inclusion of the sub-tasks on and off. In report (mostly the issue navigator) there are a set of "sigma" fields for pulling the accumulated numbers out. If that is not what you mean, then you are going to need to explain how you are measuring "progress" - what's the quantifiable…
-
Text and string fields render as html in Jira and give you plain text to work with in your application. Use a text area field. I don't understand what your problem with html is, you need to explain why it's a problem and why your application code can't handle it.