Comments
-
The fact it hasn't been closed recently means that assumption is incorrect. Atlassian started an initiative to review all open requests in their Jira a few months ago, and this one survived the initial run of "close if we're sure we won't do it"
-
Ah. You shouldn't do that. If you don't want a field on a screen, remove it from the screen definition.
-
I don't think 3.1.4 has that function in it. You'll need a later version.
-
You'll need to inject javascript to do that, but doing it manually is an unsupportable and unreliable nightmare. You'll be better off using the Behaviours module in Script Runner to do it, although I'm not 100% sure it will work with whatever you mean by "database field"
-
There are other add-ons that work with links, but this case is very specific and I don't know of one that quite meets it (ScriptRunner allows you to write code inside the application, so it can do it)
-
Ok, I think this hinges on what you mean by "include". What does an issue "included" in a project look like?
-
Have you worked through the troubleshooting doc Mizan pointed to?
-
The whole point of watchers is that they get told about issue updates, and Jira doesn't care if a user is internal or external, just that there is someone to notify. You've told it to notify these people. The only way to differentiate the emails would be a rule on the outgoing mail server.
-
When you "added an issue in the database", did you do it properly? Jira was offline and a full backup taken before running the (at least) 4 inserts and updates, and a full re-index done after restarting? If not, then you will need to revert all the changes you made, very very carefully, while Jira is offline. Ideally, go…
-
What text do you have in the description of the first field? Can you check that it's completely empty, no whitespace etc? Also, try renaming the first field so it has a name that fits on one line. This is a temporary test, just to see if that affects the layout at all
-
In most cases, this metric will just tell you how good your estimates are, it's not going to give you "efficiency". Basing commission on it is going to give you one of two problems. * If one person/team sets estimates and another executes, you're going to demoralise and lose the people doing the work (unless the estimates…
-
I assume you mean an application link? If so, this error happens when the url given is not the base url of a working Jira, or when that url can't be reached because of a network or proxy problem. You'll need to make sure there's a Jira there, that your url is correct and that you can reach it from the Confluence server.
-
Yes, Jira Agile is an add-on for Jira 6 (and below) No, for Jira 7, Software is an Application you add to a Jira Core install. Yes, Confluence works with both, assuming a recent version
-
It's been a fixed-width field for a long time, and probably isn't going to change. I'd like to see a wider format (and frankly, putting the project code first, although I suspect that's because I have been steeped in Jira for over a decade) I can't find an improvement request to widen the field, might be worth raising a…
-
I do not understand "turned it off, updated and then back on", but I am glad it has fixed it for you!
-
Have you added the component field to the Create and Edit screens in the project's "issue type screen scheme"?
-
Wait for Atlassian to fix Confluence. That's the only supported answer I have I'm afraid.
-
No. See https://confluence.atlassian.com/adminjiraserver/installing-jira-data-center-938846870.html
-
There are several ways to do this, but in most cases, you have * Used the workflow configuration option in a "simplified workflow" to say "this status should be configured to be 'done'" * Put a post-function on the workflow that sets it * Put the resolution on the transition that moves them into the sprint * Scripted a…
-
Issues are lists of issues in the project. Backlog is the list of issues that are selected by the board filter, and are ready to be worked on. Have a look at the board configuration, it should give you the filter for what it is selecting for backlog and the board. You will also need to check that the columns match (an…
-
Add-ons for Cloud validators are not structurally possible yet!
-
The default admin account is the one you set up during install. Have a look through https://confluence.atlassian.com/jira/retrieving-the-jira-administrator-192836.html
-
You can add Service Desk as an add-on to Jira, yes, whether it has Agile already or not. Confluence of any version from 5.6 to 6.5 can be installed separately and connected to Jira 6.3.4 The current version of Service Desk is for Jira 7 though, and it's an Application now, not an add-on
-
You clearly are not setting it to a valid user. The error message clearly states that it is trying to use the default assignee in the project, and that user does not have the right to be assigned issues. Go back to the basics: What user is performing this request? Do they have the right to assign issues? What username are…
-
Putting a Jira and Confluence database in the same space will corrupt both of them irretrievably. They must have separate database areas.
-
It is for me. You'll need to explain more.
-
I'd use the getFieldByName and setRequired you found in the table of help. It's good to read and learn new stuff.
-
Yes, it must be the IIS settings. I can't pretend I know why it has to be so complex in IIS (It's two lines of config in Apache and one in Nginx), but yes, you will need to adjust the rewrites so they include the ports.
-
Have a look at the link Bhushan gave in his last comment. JQL is a language for doing advanced queries (filters) in Jira. You don't need specialist knowledge, Jira's advanced search does quite a lot of hand-holding, pre-filling and auto-suggesting things for you.
-
You'll need to write a converter - Jira's REST API hands you comments as stored, there is no conversion routine available.