Comments
-
We can't help you with that, we know less about the instance than you do! I'd ask the people who asked you to use it.
-
MySQL doesn't support those extended emoji characters with JIRA. Or the other way around - JIRA doesn't support them when backed by MySQL. I don't know which one of those the fault lies with, but it's one of the two. Either way, you can't use extended emojis with JIRA.
-
Change the project lead to the person it should be, or have a look at the notification scheme.
-
The assignee field. Look at the issue and check the "history" tab.
-
I think you missed something in the documentation - you can only import from the same version data. 6 to 7 won't work directly, you need to takethe 6 data and upgrade it to 7, then export it.
-
You don't need it on Cloud systems any more, so Atlassian have removed it.
-
dbconfig.xml is the file you need. You need to get through the configuration with a valid SQL configuration in the gui before this file will exist. You have to use a static port, even with a "named" source.
-
A security level of "none" will not hide an issue. Unless you've created a level deliberately called "none" and then not put the right groups of it. As an admin, you should be able to adjust the level to allow people to see it.
-
In case you think I've given up here, I have not. It's just that Arthur is explaining it better than I can!
-
That's a good call on the custom field, there might have been a clue in a user-picker. I'm thinking it's more likely to be something in the data that is stored for them that relates to the "configure fields" option. I think that might be in one of the "property" tables, and linked to his id.
-
It's not something Confluence has in it natively. So it's either your browser, or an add-on. Have a look at the list of add-ons you have.
-
I'd say Jira may be overkill compared with Trello. Trello is a simple task manager, not a lot more complicated than the set of post-it notes on my 'fridge. Whereas JIRA has a full workflow engine, flexible fields, powerful permissions and so-on - it's aimed squarely at teams with distinct process, and many teams. But if…
-
Check that the base url includes the https: prefix (in general config)
-
I'm afraid you can't. Your admins have set up far too noisy schemes for the projects and they'll need to fix them.
-
Check the permission scheme for the project - you need "delete issue" permission before it will appear. However. Don't. Deleted issues are gone, permanently, forever. Delete the wrong thing and you could spend days arguing with backups, trying to get it back. It should be limited to those you trust to get it right, or…
-
It was my reading, not your writing. It's not about performance, it's usability. The feeling from Atlassian was that the strikeout gets in the way of visibility, and should only be used when the information that an issue is resolved is directly and immediately useful. In a search, it should not matter that much, as if the…
-
If you're getting fields appear that you have hidden in a field configuration, then the project/issue is not using that field configuration. Take note of the issue type you are trying to create/edit. Then go to the project admin and look at the field configuration scheme. That should tell you what field configuration is in…
-
Oh, hang on, you're not talking about the resolution being set, you're talking about the strikeout appearing in certain places. It does not appear everywhere. If the resolution is naturally on screen (such as in a filter result), it's not struck out. Sorry, I missed that!
-
You're still going to have the same problem that add-ons can do all sorts of things, but macro usage is solve-able. I have https://community.atlassian.com/t5/Confluence-questions/Scan-Confluence-instance-for-macro-usage/qaq-p/117041 in my bookmarks - Davin's macro works really well.
-
That's not how JIRA behaves. I suspect you are not using the system resolution field.
-
Two problems * That's too old a version to have an "installer" or "binary". There are "evaluation installers", but I remember those being "fun", and not suitable for creating production systems. * 3.5.17 does not exist. Go to https://www.atlassian.com/software/confluence/download-archives and download the highest version…
-
What do the logs say?
-
There's nothing running there. Could you tell us what the system is doing?
-
No, as I said, I really cannot replicate it. I either have to remove project admin rights from my account or share the workflow to disable my edit option.
-
I've seen this on older JIRA installs. When you checked in the database, did you find only one issue type record for each of the broken issue types? It used to be possible to create two types with the same name in some circumstances, and then when you delete or rename one of them, it hit the wrong one. This left issues…
-
https://confluence.atlassian.com/doc/migrating-to-another-database-148867.html is the first hit on every search engine I've tried.
-
No, I'm not aware of any. Structure can help you with it though, as can Portfolio. They're not quite the same, but do enable similar linking.
-
I suspect they might be coming from Capture. To check this, nip into Admin -> manage add-ons, disable the add-on, check if you can still add them (you should not be offered them if the add-on is disabled). Then re-enable the add-on If my guess about capture is wrong, I'd try the same trick with "hide time tracking",…
-
Ok, that's a nice clear simple filter. So, the next questions: When you are using the default workflow, do you mean for the main issues (which won't create subtasks), or for the sub-tasks themselves? Does your board have any unmapped status in the "column configuration"? When using your new workflow, can you try…
-
Yes, that's because you have installed two separate servers. You need to grant your duplicated users SD access on the SD server, and Software access on the Software server.