Comments
-
create a new language by taking the current language .jar out of the jira-server download as a starting point and replace Epic (and Epics and sometimes epic) with Feature (or Features). Languages are added as Jira-Plugins and everyone using this language then has the SAFe terminology. Everyone not using the new language…
-
This is because you have not added any code or automation to do it. Jira does not make assumptions about people's processes other than "ask if you want to close a parent when the last open subtask is closed".
-
Alexey gave you an answer for Jira Software because you didn't tell us it was a Trello question. Jira is a lot more powerful than Trello, and has very flexible permission schemes for users and groups. For Trello, you just need to check the individuals you give access to in each board, not groups, as it doesn't really have…
-
The ... towards the top right of your board. I like the idea of using an image to say "look here for config stuff", rather than a block of text, but a quiet ... is a poor way to do it. I do not know how to improve it.
-
You should follow the instructions for a standard SQL database migration. Take your 3.5 install and export it to xml. Move it over to a supported database for 3.5 (See https://confluence.atlassian.com/display/CONF35/Supported+Platforms ) You do not need to worry about the evaluation licence. All they do is "time bomb" -…
-
This community is a good place to get an answer when you are not seeing how to do something. Could you tell us what your board is looking at, and give us an example of an issue that you think should be appearing? Yodiz is quite nice in some ways, but you are going to run into the same problems with it. You really need to…
-
The box you are pointing at in your screenshot is a search for quick filters. We need to see 1. The board filter. Not a quick filter, but the filter that decides what issues to draw into the board. It's in the "board config" section 2. An issue you think should be in the backlog, but is not.
-
Epics do not really "contain" stories, they're more of an association. As any given Story that is associated with an Epic could be in any project, it doesn't make a lot of sense to say "if we move an Epic, drag all the stories with it". It might not be appropriate for some or even all of the stories. Your instinct about…
-
It's always been time consuming. Apps for Cloud and Server use totally different frameworks. Whilst there's core logic and sometimes a bit of code you can share between them, on the most part, any app that is for both is two independent products.
-
Not my choice, I'm not Atlassian. I'm not fond of the new UI, I think it needs quite a lot of work in usability terms. It's clearly less friendly than the old one in some ways. That said, it could work. I suspect part of the Atlassian approach is "don't clobber the server users until we've got it right"
-
You can do that for customers, that's one of the main routes Service Desk uses for communicating with customers. But you are trying to add people as users, not customers, and you've already got the maximum number of users defined. How have you configured the incoming email for the service desk project?
-
Do you have a -1 priority in the priority list? Do you have any scripting add-ons installed?
-
This is exactly why Confluence has always had an "include" macro. When you identify a duplicate, delete the entire body of the duplicate and replace it with a simple "include: source of truth" macro.
-
Ok. The view you are seeing is a standard project view. That means it is either not a Service Desk project or the person looking at it is not an Agent in the project.
-
This is not a "customer". In Jira, "customer" means something very specific - it's a user who can use the Service Desk portals, but NOT the rest of Jira. You don't need licences for "customers". However, you do need them for Jira users (Agents, Software users or Core users). You have run out of licences for the role you…
-
Ack, sorry, I just noticed, you're in two different projects there. IT Service Desk and Zoe Service Desk. Check which one you are in is still Service Desk and you're an agent in it.
-
Start with a look at https://confluence.atlassian.com/adminjiraserver075/upgrading-jira-applications-935390934.html I would strongly recommend that you take the path 6.3 -> 6.4 -> 7.0 -> 7.whatever-you-aim-for
-
It looks like either 1. An admin has swapped the project from a Service Desk type to a Business type 2. You are no longer a Service Desk agent in that project (Or someone has disabled Service Desk!)
-
I'm afraid you are going to have to give us more than that. What did you do that caused the problem to appear? "correctings issues with Confluence" does not tell us anything.
-
From what I've heard (unofficially), it is pretty much certain that it will not be before the next US Summit (spring 2019), and don't bet on it being one of the things announced then either.
-
Just pointing out bad practice, and that a good admin will remove that sort of thing as soon as it's noticed. And it is one thing Cloud gets right, stopping horrid broken bothces.
-
I'm afraid your summary on your other question is correct. Because you are on Cloud, you are at the mercy of their translations, you will have to wait for Atlassian to correct it. I would do what Warren says, so at least you have something to track with them.
-
Except that 1. Injecting javascript like that is a bad thing to do 2. It doesn't work on Cloud
-
Is there a transition between the parent task's status and a status in the "done" column?
-
Are the issues resolved and the gadget's "ignore resolved issues" box ticked?
-
I can confirm that they're not only unsupported, they also fail.
-
Alexey is correct. It's not losing anything. User 1 commits a change, then later, user 2 commits one. There's nothing lost. User 1's changes are in the history.
-
Advanced search: <field name> is empty
-
Um, I don't quite see that - you say they're not sub-tasks, but then they are sub items - which is a synonym for "sub tasks". Yes, you need code to do this. I don't know of any apps in the marketplace that will do this for you, but I would take a look before diving into code.
-
How are you telling Jira that an issue is "part of a team" (or not part of a team)?