Comments
-
Yes, you need a Jira isntallation to run Service Desk on. However, if you download Jira service desk from the site, it is a bundle of Jira and Service Desk, so you only need to install that to get both in one go.
-
https://confluence.atlassian.com/jirasoftwarecloud/configuring-filters-764477988.html You can go to board config and press "edit filter"
-
That's not Jira. You'll need to ask the provider of this system.
-
Yes, as I said, it kills ranking.
-
Jira doesn't support that structure. It's Issue and sub-task. With Jira software, you can do Epic, Story, Sub-task. With Portfolio, you can use themes and initiatives too.
-
That's good, you only have two edits, one is about configuring logging, the other is the application properties which is normal, it has the jira home set in it. Which mostly means you don't need to worry. Keep a copy of both before upgrade. The check on the add-ons is quite important - some may not have an updated version…
-
You could add "order by created" to the board filter, but this will stop your ability to rank the issues.
-
What collaboration section?
-
No, it's effectively hard-coded, I'm afraid you'd have to hack into the core coding.
-
And? Errors? Description of actual problem? What project documentation? Who's Jira? For all we know, it's because there's a penguin asleep on your keyboard.
-
Atlassian do not, but their partners do - see https://www.atlassian.com/partners/search?page=1
-
No, it is not changing the names. It is creating new workflows with new status.
-
Er, I think you're in the wrong thread - this is about Sourcetree (which has never had the option to "opt out" - you upgrade it to a version which has a poor UI)
-
It's the right answer though. As you can't edit labels.
-
It's been included in the system information page since Jira 3.0. In later versions, when the page started to get too long, it was grouped in with other "file paths".
-
See Amanda's answer.
-
Ok. Confluence does not recognise that as a valid link, so it does not save it as a link. That's why I asked what you had customised, because you need to hack the code in confluence to tell it that this should be treated as a link.
-
Grant the users "view workflow" in the permission scheme for your projects.
-
Yes, the number is telling you how many issues are in that status. If it is zero, then no issues are in that status, so the change will not actually affect anything.
-
Ah, ok, you've looked for the wrong thing then. Jira has a default home directory in a moderately sane place for most systems, but because it's a server installation it allows the installer to change the default. Either way, the person installing it will have chosen a home directory for it. Yes, some place it in a user's…
-
The page you cited is not about changing the properties file. Generally, you shouldn't need to change that file, it's not a "simple action", it's a deliberate thing for a handful of people who have non-standard needs do. If you don't know what you're doing here, I have to question why you're even looking.
-
If you'd bothered to read the documentation that is telling you to amend the properties file properly, you should have seen something along the lines of "you may need to create the file, as it is not needed by a default installation"
-
Nope. See Jobin's link. Given the age of it, I'd say it's way down the list of priorities for improvement (it's not a "bug", there's nothing broken or wrong, it's just not something they've done)
-
Look at the issue history - it will have recorded who changed the link if it was a change of link. If the Epic has been deleted, then you're probably a bit stuck, even the database won't tell you who did it (because it has nowhere to record it as the issue has been deleted). The audit log, if enabled, may say, but that's…
-
What does the log say the issue is?
-
Yes. A board shows all sprints that apply to issues on it.
-
Yes, the error is that the user is not there.
-
Look in "system information". It will list * Your add-ons * All files that have been edited away from the off-the-shelf installation files (you'll need to check each one to see what your ex-admins hacked)
-
Inaccurate description of problem, and answered on the duplicate at https://community.atlassian.com/t5/Jira-questions/Publish-Workflows/qaq-p/750390#U751307
-
Ah, ok, so you've asked an inaccurate question. There is no "replace for specific issue types" going on here, you're asking about the mapping of old status to new. When you replace a workflow, Jira has to check the status the old and new workflows use. If a status does not exist in the new workflow, it needs to ask you…