Comments
-
There's nothing to stop you putting Story Points on issues that you are tracking through a Kanban board. It won't affect the Kanban board or add any additional functions, as Story Points are not used in Kanban, but there's no harm in adding them. You might find it easier to have a Scrum board as well as the Kanban board,…
-
You can use the built in {include} macro to do whole pages
-
And they have "email me on my own changes" enabled too.
-
1. Jira doesn't notify watchers when they are added to an issue. It's buried in the docs somewhere and there's a request to have "added as watcher" as an event somewhere, but it's not been implemented yet. 2. That sounds broken, if you've got all-watchers for all-events in your notification scheme, then they should be…
-
Ask an existing administrator to add you to the administration group. Note that you don't get system-admin on Cloud, it's restricted to Atlassian Cloud Support only.
-
Yes, sometimes I fall into the day-to-day assumptions and forget to explain properly, sorry.
-
I was assuming you knew that you didn't have System Administrator access, and were talking about the Confluence Admininstrators.
-
You'll need to contact Atlassian support if none of you have administrator access. Https://support.atlassian.com
-
The Asana source data is missing information JIRA needs. I can't tell you much more than that.
-
It looks like the data you are importing has one or more missing pieces of data. You should read more details about exactly what from the log file.
-
That IP address is the other one you need to add to the list - ALL of the proxy IPs should be listed in the match box, not just one of them
-
No, there's no refresh or anything needed. Once you've said "use workflow X for project Y, issuetype Z" that's it, it'll use that workflow. Start by checking the conditions on the two "put on" transitions.
-
Best way to do this is a scripted field with the script-runner.
-
What you're proposing with tabs sounds like absolutely the right way to start. Move the unwanted fields to tabs for display, and then delete them from the edit screens, and you'll lose nothing at all. I would do that and then leave it for a few weeks maybe. Because you'll be able to judge the reaction of your users to not…
-
Two parts: Removing the field from the screen, or even from the field configurations, or field contexts, will not lose the existing data. Removing it from the screens will not affect search or reporting. Removing it via field configuration or context will remove it from searching and reporting, but still not damage the raw…
-
Then you're asking completely the wrong question. The single most important tool that you have for diagnosing problems is the logs. If you want people to answer without reading the logs, all you can really say is: 1. Are you sure it is running? 2. Can you access it from the local machine? 3. I need the logs. If you're too…
-
So what have you changed? (Assuming it worked before). Is it running? What do the logs say? You really do need to do some basic information gathering, and share it with us, if you want our help.
-
That's ok, nor can we. You really do need to give us a LOT more information. Is it running, what do you get on screen, what access did you try before, logs? Your question is a bit like ringing up a garage and saying "my car doesn't start". The mechanic doesn't even know if you're in the same place as the car, let alone…
-
No. We're not support, and we're not Atlassian, we're a community of end users. We don't have access to the licencing system. You'll need to contact support for this - https://support.atlassian.com
-
This usually happens when you try to put a developer licence for a plugin into a system that has a production licence. (And vice-versa) Check what types of licence you are using for both Confluence and the plugin.
-
They might look identical, but that's just the name - there's 10 totally indpendent objects in the database. As the project admin you can maintain the list of components, but only from the project admin section.
-
Short answer is that you can't. Components belong to separate projects, and so have different possible lists, so you simply can't set it for two projects at the same time. On the second point, no, maintaining component lists is done in the project header by someone with project admin rights.
-
Generally, sub-tasks are quite small, discrete pieces of work that are pieces of a story - the information on the story is used as well as the stuff on the sub-task. It usually makes sense to be able to see the whole story and the other parts of it. Same basic idea for Epics, although most find them less useful on working…
-
Because humans get really annoyed when you mess with their stuff without talking to them first.
-
JIRA cloud has all the facilities that Server version does when it comes to "inputs". In most cases, the simple answer is "look at the REST interface". But you'll need to explain what you're trying to "integrate" before we can tell you much more. No, there's not a lot you can do with SSO for JIRA Cloud. It's got your…
-
That's an immense amount of hard work. First off, Jira 6 data, while similar to Jira 4 data, is different enough that there is no chance of a simple export being even remotely compatible. You're going to need to extract, manipulate and recreate the data. The method you pick to do that is going to depend on how much data…
-
I'm not sure Atlassian will do it, but it can't harm to ask (let us know if they do do it!). Raise a support request at https://support.atlassian.com
-
Yes. When you change an issue, whether it's a single edit or a bulk-edit (including move, edit, transition etc), JIRA re-indexes the issues affected. If a user has a page open with a dashboard report or query open, it won't be refreshed with changed data, but the next time they use it, it will re-read the issues and hence…
-
Check that you're using the right version of the plugins for your confluence, then try to re-enable them in the plugin management screen, reading the log for the errors that will tell you why they are not loading.
-
It's a turn of phrase, a gentle hint that if you'd typed "jira database" into the search in the documentation, you would have found it.