Comments
-
Is your "done" status mapped into the very last column on the board?
-
Ah, sorry, I got too focussed on SR and didn't re-read the question properly before my last post. The tutorial you used to create your web-panel shows you how to create a panel with some text that is calculated from some system and issue data (the current date and the due-date on the issue). Now, that is not "adding a web…
-
Yep, this is one of many reasons I recommend doing reporting properly (with apps built for it, or asking Jira for data over the REST API) - the database is the worst possible way to report on Jira data. But, if you insist on doing it the hard way The table you are looking for depends on the type of field it is. My guess is…
-
You don't need to assign issues to people for them to be able to log time on them. (And you never want multiple assignees on an issue too, but that's another conversation) Check the project permissions, you should find "log work" is one of the permissions, just make sure your people are included in it. As an example, I've…
-
You cannot delete an account that is responsible for ownership of one or more Cloud sites. Atlassian cannot have unowned services, it's illegal in a lot of places. Go to one of the applications under nikhil-grazit.atlassian.net, log in with this account you want to delete, and hit the admin cog at the top right, selecting…
-
What do you mean by "effector"? Automation? Script? Listener or function from an app?
-
Site admin gives you the ability to admin the site, but not necessarily automatically all the applications within the site. Equally, Admin on an application may not be tied in with site/person admin. Could you give us the url you land on when you click the users tab in admin? (Obscure your site name if it's in there, we…
-
Your instinct is correct - any time you change the database outside Jira, you absolutely must run a complete (locking, not background) re-index. This might not be the problem in this case, but you stand no chance of finding or fixing the actual problem until after you have re-indexed in full.
-
Um, I'm a bit confused. The doc I pointed to was about getting access via a local account, it had nothing to do with Crowd. What happens when you try the local admin recovery account method?
-
Ok, it's quite likely that your system is still trying to use a crowd-provided account and not being able to reach crowd means it can't. Best bet at this point is recovering an internal account - https://confluence.atlassian.com/jirakb/restore-passwords-to-recover-admin-user-rights-972329273.html
-
You can put all sorts of things in them - see https://scriptrunner.adaptavist.com/latest/jira/fragments/WebPanel.html
-
Not yet. The workflow isn't quite the discrete object a (company managed) workflow is and an export/import/share hasn't been written yet.
-
Yes, sorry, I over-egg that one. The point is not that "move" is right or wrong, it's an attempt to help people see what it is doing behind-the-scenes. Also the point that the backlog *is* the board, just a different view. In Scrum, the board is a different view of the issues at the top of the backlog, inside the sprint.
-
Ah, ok, then we need to look at exactly what it is doing, and why it is choking on the content! One other thing I forgot - trying the { tests might help us identify it, but you might also want to quickly check admin -> user macros. If it is a user macro, it should be listed with awp-include on-screen somewhere.
-
Ok, so you're not using Epics the way they are built for. That's fine, but you can't expect a tool that handles them as intended to work properly with it. The answer to "what do we need to do to finish out this Epic" is supposed to be the same every time you ask - "deal with the stories inside it".
-
The name of the macro is awp-include - it's an internal name, the error messages don't give us the human display name (not all macros have these) Next thing I'd try is adding a new one to an empty page to see if we can find out where it is coming from - on a new page try typing {awp if it really is a macro, it should start…
-
Not really, Epics aren't really things you would put on a board, as they're not actionable items themselves (and their in-progress status is not something you set, it's determined by the status of the issues they contain - an Epic is in-progress by virtue of having one or more of its stories in-progress)
-
Note that the "service management" is not generally intended to have every user as an agent. It is very likely that your usage would be more like 30 Jira Software users - as what Dave said 4 Service Desk Agents who are also developers - $960 a year.
-
It means what it says, it's tried to do what the macro is telling it to do, and it can't render the result for some reason. Try editing the page, and then the macro within it - are the settings for the macro valid? Does the preview work?
-
Hmm, I checked again and I get the same now. This is odd. I've asked Atlassian to take a look.
-
Welcome to the Community! No, this is not possible. Boards are not a container for issues, they are a view of a selection. The issue key is determined by the project it is in (projects are the issue containers), and it is the unique identifier for an issue (for us humans) You can create boards that look at many projects,…
-
Yes, you said that already, but you have clarified enough for me to be able to add to my answer. The best/easiest way to do this would be with a listener. Look to scripted listeners, as you'll be able to write code in one of them that pokes remote systems. There's some examples over…
-
What are you using for user accounts? Is it Atlassian Accounts, Google or Atlassian Access?
-
Where? I mean, where are you wanting to "get" the event? I can probably answer this without knowing though. Events are intended to be a stream of notifications that things are happening in Jira. They're announcements for things to read if they want. The way to read the list is with "listeners" - they (selectively) read the…
-
No, because it's an uncommon event and not useful for 99.99% of issues. And it's in the history, so you don't need a field for it.
-
No, we're not Atlassian support and we have zero access to the back end where this error is being recorded. I don't know what you mean by "I can't find the url" - I can see it (at least the message that I do not have access), and I can paste it into the field while raising a support call (obviously, I can't submit the…
-
This is the crux of the problem: " I can't since the sub tasks should be a part of different projects, each touching a different service and therefore a different JIRA project." You need to decide if these issues are sub-tasks or not. If they really are a part of a bigger issue, then your projects are set up incorrectly.…
-
I suspect that will simply be closed with "go ask the app vendor", this probably isn't an Atlassian problem, it's happening in the Misc Custom Fields app.
-
Your server is not using your Atlassian account for login, your login to www.atlassian.com is irrrelevant. You need to log in with an account that was in use in your "old database"
-
You can create your own issue type to represent initiatives if you want, but it will be at the story level, not another layer in the hierarchy. The usual way to do initiatives as part of the heirarchy is with Advanced Roadmaps (Portfolio), but you could look for other apps such as Structure, Big Picture or even Jira Align.