Comments
-
Welcome to the Atlassian Community! My understanding is that because the apps are not provided by Atlassian, they will need to get their own certifications. At the moment, there's no point - they run on top of a non-certified platform, so they can't be certified until after Atlassian is.
-
Welcome to the Atlassian Community! What changes? Where are you looking for your issues? How are you looking for your issues? What error messages are you getting (or behaviour)? Have you spoken to your admins about it?
-
Welcome to the Atlassian Community! I don't quite understand the question - your screenshot is of a valid working hierarchy of Initiative -> Epic -> Base level issue -> Sub-task. What makes you think this is not working?
-
No, because there are too many complexities in explaining them. You need to simplify your workflow to the point where your users can't get it wrong, or train them on its complexities.
-
Indeed, if you put the rank field on screen, and managed to make it editable, it would be completely useless to you - your people would have no idea what to enter into it.
-
This would be utterly useless to you, as the number would have to change in almost every report you would run. If you mean you want a numeric id for an issue, you can get one - the issue id in the database is numeric and unique, but it is sorted in creation order, can't be searched for, not sequential, and would not let…
-
This is not really an error message (it does not mean anything you can point at and say "that went wrong"). It is a marker that goes into logs and monitoriing systems, thrown when similar errors occur in different Cloud systems. It's for Atlassian to group similar errors together. You should report this directly to…
-
No, there's no way to change a field type in Jira (albeit on server you can do some changes with database access, but you can only go single to multi, you can't convert multi to single)
-
I am not sure you are understanding the point here, so I'll try to explain it a different way. In your last screenshot, can you please circle where the transition is shown? Note that the "Done -> Done" type things are not transitions. They are showing the target status.
-
One of my favourites ;-)
-
Love it! Reminded me of https://www.youtube.com/watch?v=9shZslfbaS0&t=3s
-
Ah, that might be an improvement actually, when the field first arrived, I don't think you could use it in the "field value changed" either! There's a technical essay on how fields work internally in the code, but the short version is that a field is a self-contained object with interfaces to the rest of the code to talk…
-
Welcome to the Atlassian Community! Category is a weird field, it's a field type provided by JWM, and there's two of them. One of them is a project category, and it only really gets used in search (you can say "category = X", and it will select for all issues in all projects currently in the project category). This one…
-
Reporting outside the reporting-specific reporting tools inside projects is mostly based on filtering. Filters don't care what the project type is, you can build and save filters that list any range of issues you want, and then use those filters in reports and gadgets. So for your cross-application reporting, you can do…
-
Welcome to the Atlassian Community! How have you implemented testing inside your Jira? Have you built something that use issues to represent cases, executions and so on, or have you got one of the test management apps installed?
-
So you're literally putting in something like nurit_hadas@yourplace.org ? Does your email have any special characters in it? (Anything other than 0-9 A-z or _-)
-
Welcome to the Atlassian Community! It's either your cookies or your browser cache. Try clearing the cookies and then restarting the browser before trying again.
-
Hiding the sub-tasks does not affect your ability to move stories around the board.
-
Look to the workflow scheme for that.
-
Space admin for space-local templates, Confluence admin for global templates.
-
It sounds like the account you are using does not have permission to see the issues. (Admin rights = admin rights, not "can see/do anything") Check the project permissions.
-
There's nothing we (the community) can do here, you need a fix from Atlassian, and "escalating" it here is just going to waste more time for them to tell us "yes, we already know"
-
Welcome to the Atlassian Community! First hit on search engines is the migration program docs at https://www.atlassian.com/migration - start reading there.
-
Welcome to the Atlassian Community! Are you using Butler with user accounts (so it reads the email from the account), or with plain direct emails?
-
Yes, I have seen this before. Account deactivation is mostly done by an automated process when the account clearly violates the terms and conditions. There are a couple of other things that can cause it, but they are initiated by a human. In every case, an email is sent from the advocate account, as you have. It should…
-
See the link @[deleted] gave us, the accepted answer is the current state.
-
None of that changes it, it's just a more complex version of what I've outlined. This all comes back to a very simple point: The board is behaving the same way as the issue view already. You can not transition issues on a board if the transition is not there or blocked by a condition. Or, to put it another way: Boards do…
-
Welcome to the Atlassian Community! I think you need to talk to our Jira admins to get access to this ADValue project.
-
The issue history does not contain the initial issue creation. So if your issues are being created with Component filled in on-screen, and ending up with no components after creation, with no line in the history saying "someone deleted it", then you have a post-function removing it before issue creation.
-
I'm not sure a 6,000 page pdf doc that will be out of date in 6 weeks is of a lot of use to anyone. What use do you have for this? I'm trying to think of a use for such a pdf.