Comments
-
Because the point of Simplified Workflows is to allow the board owners to change the underlying workflow, and you don't want that workflow changes to affect other projects. It would be slightly more efficient to share a simplified workflow with all the projects included in the board, but that causes headaches, as boards…
-
They are not directly comparable. Agile is a set of guidelines that give you a time-boxed iterative approach to developing things. SAFe is the "Scaled Agile Framework". This is easiest to think of as one approach to handling multiple Agile teams. The Agile framework is all about one single team working together to develop…
-
Ok, you can use evaluation licences to get started - they last 30 days each, and you can extend twice before having to talk to Atlassian. A better option though might be to just pay for the $10 licence and only have (up to) 10 users while you configure it all (I can't imagine it would take more than 10 admins 90 days to…
-
Yes, if Dave is not on the screens in use, then Dave will not appear!
-
You're going to struggle to do this - Jira does not do it off the shelf, it works on the principle that a Jira administrator is a Jira administrator and their job is to administrate the system. If you want to limit administrators, you're going to have to remove their admin rights completely and then write your own version…
-
Something is reading your database looking for the version of the database, and assuming it is an AWS aurora database. Confluence does not do this.
-
Your images seem to tell me that you have gone to completely different places in the application. From your original question, /wiki is not the same place as /wiki/discover/all-updates Could you show us a like-for-like comparison rather than two different parts of the application which should be different?
-
The out-of-the-box workflow works with "assignee = currentUser() and resolution is empty", so I'm a bit stuck on what is wrong here if you're using it.
-
Permissions are just one reason you might not have an option. I wanted to mention it in case it was the problem here, and if other people land here.
-
You can translate it into other languages, or directly hack the language file you are using (which leaves you unsupported), but I would recommend that you do not waste your time on it. It's going to take a bit of effort, but also confuse people who have used Jira before and make supporting it more difficult. I can't think…
-
Point 2 on @Kristen Roth question is the most important one to me, although I would like to expand on it. Listen, properly. Don't be afraid of feedback, clamming up, reaction, provocation, retreating into a shell, whatever you get from trying to listen, your own reaction to hearing things, whether it works or not first…
-
I guarantee you Daniel: Every word you said to me has passed through my eyeballs and through my conscious mind before I reply to anything you've said. You have demonstrably failed to extend me the same courtesy. Please. Read. My. Full. Earlier. Comment. Basic reading comprehension combined with the simple courtesy of…
-
One thing that Atlassian do is "simple" licence schemes. Not in the sense that they are simple to understand, but in the sense that they don't play tricks like bait-and-switch or disappearing-discounts. If it's more complex than "what is on the website", there might be some room to talk, but it can get slow (and they tend…
-
No, we're still in the same place. You have missed my points, over and over. I can't work out a way to explain them in a way that you will understand, and I apologise for that failing. All I can do is to quote someone else who gets it right (while ignoring their own advice) - "Read it properly, and you will learn how it is…
-
Sorry, I was not clear. Does this project lead have Jira admin rights? (These are not delimited by areas of business - you are either an admin in this whole Jira system or you are not) You say that this person can create projects, which strongly suggests that they are a Jira admin (or the upper layer of "Jira system…
-
This is what confuses me. You say "the transitions to those status ... are not the status options I'm using in this workflow". Those transitions simply cannot be there unless you have their target status in your workflow. You might not want the status there, but that is different (and means you need to edit your workflow).…
-
The "done" status may or may not contain unresolved issues. In Jira, Done, Resolved and the StatusCategory have an uneasy and complicated relationship which can be very inconsistent. Given a few minutes I could configure a Jira that allows me to have an issue that is "Unresolved", "in Progress", "to-do" and "Done" all at…
-
Actually, you should not need to worry about logging levels just yet - most issue creation failures will automatically throw errors into the logs. What error do you get on screen when it goes wrong? Can you match anything to the time stamps in the logs?
-
I think you've completely missed the point, and neatly condensed that down into the phrase "user hostile design". The problem is that sidesteps every main point - your evidence of "user hostile" adds up, but nothing makes it "user hostile". It all means "while people don't get it, it's stopping them breaking stuff" You say…
-
You need to work out exactly what you did so you can reverse it. I am not 100% sure from what you have said. I am guessing that you created a new (management) project using shared configuration and then edited the workflow. If that is the case, the workflow editor would have worked in draft mode, and asked if you wanted to…
-
Archiving projects is currently only available on Data Centre installs, not Server or Cloud. You can partially imitate an archive by hiding issues with security schemes, but that just hides them from people, doesn't give you much else.
-
Workflows do not "go to fields". The (part of the) workflow you are showing is of the transitions from Open to other states (status). The transitions are all "valid", or they would not there. Are you sure you are looking at the workflow you intended to look at?
-
I am confused, on two points. You say you want to see incidents and stories in the Epic panel? The Epic panel is for Epics, so I do not understand this requirement. You also say you could see them before, which makes me think you are not looking at what I think of as the Epic panel? You have no access to some projects.…
-
This one is hard to explain, so I'll try a worked example. Imagine * You have a field called "Dave", which takes strings * Dave should appear on (issue type) Bugs, but not on (issue type) Features. * You have a Bug with Dave set to "mydata" * You're going to change the Bug to a Feature Now, there are three rules for a…
-
Yes, but you can't do it yourself. If you raise a support issue with Atlassian, they can change it over for you (obviously, this is something they will not do a lot, only occasionally). Visit https://support.atlassian.com/contact
-
I don't bother filtering boards for this. With a Kanban, a release clears the issues out of done, and with a scrum, done things drop out when the sprint ends. Filters for a whole project, I want to include the done ones. So a question is where are these a problem in boards? (I know growing projects is an issue for searches…
-
Jira does not have multiple assignees. The assignee is a single person to prevent the (guaranteed) problem that "someone else was doing it" You will need to add a custom field to capture multiple associated groups or users. Jira notifies people according to the notification scheme and puts stuff into the activity streams.
-
Because moving an issue keeps fields unless they are specifically excluded from the issue type you change it to. Only "custom field context" matters here, field configurations and screens will not destroy the data if they're not set to show a field (they can hide it, but they won't destroy it)
-
You cannot do this yet - all Cloud systems still need to stay on <something>.atlassian.net But Atlassian are working on custom domains.
-
Note that if you don't have "manage apps" in there, then you are not an admin and you'll need to talk to an existing admin to get your app added or your permissions updated.