Comments
-
Are you sure that command is running it as the right user? Have the permissions or ownership of the files and directories changed after you ran it?
-
The problem is a misunderstanding about what a sub-task is. They are a part of their parent issue (story), not a separate item, and hence not a sprint item. When you're doing a sprint, all that matters is the completion (or not) of sprint items. Estimates on sub-tasks don't count as anything other than as part of their…
-
Welcome to the Atlassian Community! Yes, this is correct behaviour, even though it looks broken at first. The problem is a misunderstanding about what a sub-task is. They are a part of their parent issue (story), not a separate item, and hence not a sprint item. When you're doing a sprint, all that matters is the…
-
Yes, you've got it right - moving a card from column to column is allowed or blocked by the workflow. A card move on a board is performing a workflow transition. To get the original question out of the way - nope, it doesn't matter if a workflow is simplified or not. (In fact, simplified workflows are just workflows that…
-
One minor addition to this. People who have JSM licences (Agents) or JS licences (Developer), have access to Jira Core by virtue of those licences. This means you can allow access like: * Alice: JSM Agent * Bob: Developer with Software access * Charlie: Only has access to Core Your licence costs for these three are 1 Core,…
-
No, it's more that "EWS is not a viable option moving forward". It may be in the future, but a glance at the backlog of open requests, sorted by the number of votes finds it having 375ish issues more desired by the end users. The age of an issue is not something that feeds into the prioritisation of the requests. Votes are…
-
Does your workflow have a transition from the issue's current status back into "open"?
-
Yeah, that's not what I get.
-
Welcome to the Atlassian Community! What do you mean by "sub status"? Jira doesn't have a sub-status, an issue is in a single status at any one time.
-
This is not going to work like that. It can't because you don't know what you need to look for. Imagine you've got a list of components, and the same list in the second project: * Dog * Bunny * Cat If someone changes "Bunny" to "Guinea Pig" in TH, then How are you catching the event that they do that? If you read the…
-
Sorry, I can't tell where you're getting that from, there's too much missing from the screenshot.
-
Welcome to the Atlassian Community! Actually, I don't think that's a problematic way to work. Assuming the Epics are large overarching things that are unlikely to get done in a sprint, and you sprint on the stories that come out of them, there shouldn't be an issue. The only headache I can see is that Epics are not sprint…
-
Problem is, it's Cloud - the issue was fixed over a year ago. You'll need to re-raise it with Atlassian. (FWIW it's working for me)
-
Welcome to the Atlassian Community! Could you explain what this has to do with Confluence?
-
I'd recommend a look at the first couple of hits on https://marketplace.atlassian.com/search?hosting=cloud&query=contracts
-
Welcome to the Community! I'm afraid the version of the Cloud software is out of our control, it always rolls forwards (premium, enterprise, and those in the middle of a migration customers can put a hold on it for a short time, but change will still happen) There's no way to "revert". All you can do is report the problem…
-
Thanks @Mikael Sandberg - reading back, I've been assuming we were talking "administrator role in the project", but I had not said it clearly.
-
I'd want to see that you are in the role of administrator for the project as a last screenshot for support, but the rest of your screenshots are telling me that there is a bug (possibly a couple) Working from the bottom upwards: * The Automation actor is you in the last screenshot * The error message is clear in that it…
-
Welcome to the Community! Yes, this is easy with JQL functions. Try created >= startOfMonth() If you want to look back to previous months, try something like created >= startOfMonth(-1) and created <= endOfMonth (-1)
-
No, I'm afraid you'll need to do your "post processing"
-
Ok, so you'll need to show us the automation, the "restriction" and what it is doing.
-
Yes, that's exactly what story points are for - helping you to estimate what you'll actually achieve in a sprint, but also improving your estimation and delivery from a sprint, by allowing you to draw in the right amount of work.
-
All sorts of things could be achieved with an "integration", depending on what it has been built for. But we can't tell you about them because we don't know which one you might be looking at. I'm afraid the question "what do you want from an integration?" is never answered by "what could it do?" in these cases. All we can…
-
Which Atlassian application are you connecting with Sonarcloud?
-
A portal is a function of a project, so they can't be "in" other projects.
-
Be aware that it is very likely to be closed with "won't do" - Jira is a collaboration tool, and limiting visibility of parts of an issue is the opposite of that!
-
It is possible to do a bit with page restrictions in the core product - put a restriction on the page when you create it, removing it to "publish", but that's very simple, and Comala is a far more sophisticated publishing tool.
-
Mimecast/spamcop are blocking stuff from an email server/relay (which is not owned or deliberately used by any particular source of email) So, if you want to get email that is coming from there, you need to ask Mimecast/spamcop to allow it through, or stop using them.
-
Drafts are drafts, they are not intended to be published in any way. Your only solutions are: * Use it as intended - publish and ask people to review (with a limited audience) * Copy the draft text out, and paste it into something
-
To order issues in your backlog and board, you will need to alter your board filter such that it sorts by the field you want instead of rank. Bear in mind that this will disable your ability to rank (because your issues won't be in rank order)