Comments
-
>My users want ability to move issues from any to any status(like simplified) but not through the board That's nonsense. A board is a view of the issues, not a container. A board "move" IS a transition. Yes, you do need to add a post-function to every "coming out of done" transition, there is no way around that. Because…
-
You need to tell us what the problem is. "I can't connect to the server" is not a useful description of your problem. It's like saying "I can't drive home" without telling us whether you can't drive, your car is broken, you're out of petrol, blocked from your car by a horde of angry penguins, or telling us where home is or…
-
duplicate of https://community.atlassian.com/t5/Jira-questions/issue-is-not-visibility-of-my-work-button/qaq-p/664664
-
Duplicate of https://community.atlassian.com/t5/Jira-questions/issue-is-not-visibility-of-my-work-button/qaq-p/664664
-
Duplicate https://community.atlassian.com/t5/Jira-Service-Desk-questions/Customer-uploaded-an-attachment-and-they-are-unable-to-download/qaq-p/664586
-
Duplicate of https://community.atlassian.com/t5/Jira-Service-Desk-questions/Customer-uploaded-an-attachment-and-they-are-unable-to-download/qaq-p/664586
-
Duplicate of https://community.atlassian.com/t5/Jira-Service-Desk-questions/Customer-uploaded-an-attachment-and-they-are-unable-to-download/qaq-p/664586
-
You need to ask your admins to "tune" the notification scheme to send you less email.
-
No, the issue view screen is hard coded to put all the system fields in the "details" area. You can move the custom fields around in their area, and group them with tabs, but not the built-in fields.
-
You can get the licence key from your my.atlassian account, then paste it into the licence key box. The server does not need access to the marketplace to do this, so I'm not actually sure what you're doing here!
-
No. A DNS system resolves the server name to an address. Not parts of a service. You've got one service running here, which means DNS has only one thing to point at. You have set up your server (and hence DNS) with customer360 as the name of the service. The projects within it all live beneath that service name.
-
Or even just read it, to see what is going wrong. Also, check the url you are trying, as a 500 error implies something is running on the server, but you've landed on an address it does not have.
-
Subtasks belong to their parent issue because they are part of it. If the parent issue is in a sprint, then the subtasks are as well because they are part of it. The most simple "report" is a search for issues in the issue navigator. Include the due date in the columns selected for display (there's a fields/columns config…
-
Yes. But you need to tell us what you want from "IT Separation projects" before we can help you more.
-
I think you might remain stuck, as you've asked a load of Atlassian users about Pokemon. Some of us play, but this is not really the right place to ask about it. We're good with Atlassian stuff, but probably much less so with Pokemon. (Certainly not me, I can't tell a Jigglypuff from a SnorkleGronk)
-
You probably don't want to remove those entries from the issues, as that would leave "closed" issues also "unresolved". There is no bulk remove, because Jira needs to check you won't be trashing your data if you do it. Rather than mess around replicating all the checks and working out which ones you could remove safely and…
-
I've had this request recently as part of a project, and the only answer we could get to was "create all issues in a dummy project and then write a horribly complex automatic move-issue-automatically" process. We went with Service Desk instead, as it simplifies things for the users so they don't need to know the project.
-
Please, forget the database. You can't write to it safely, and "safely" is going to take you months, if not years, to work out and prove. It's also designed (well, grown up as anyway) as a data store. SQL is the single worst possible way to report on issue data. Use the API to do all writes and most reads. That means going…
-
This does mean users trying to access it on the second domain might run into display problems, and then end up accessing it over the first domain within a few clicks. Seriously, not worth doing.
-
Both looks have strengths and weaknesses. My gripe with the new style is that although I find it more slick in general, and would be perfectly happy with most of it, the loss of the page tree in most places is a disaster for navigation.
-
You will need to find or write some code to do that. You haven't said when you want to do it (transition, during create, during edit, etc). That probably determines how you're going to do this.
-
You will need to find or write a customised "email handler" that can read the email in full and fill in the fields.
-
No, they're issues, like any other, as far as notifications are concerned. But you can do it. * Copy the workflow you currently have for Epics, so that you have a new one just for Epics. * Associate that workflow with Epics in the workflow scheme. * Go to Admin -> Issues -> Events, and add a custom one called something…
-
Try the <sigma> time spent.
-
Atlassian keep them all (well, the public ones) in Jira over at https://jira.atlassian.com/secure/BrowseProjects.jspa?selectedCategory=all&selectedProjectType=all
-
As an admin, go to custom fields and add a cascading select field. Then go to the service desk project and map the field on to the portal, like the other fields.
-
So, when you started this, you had a workflow with transitions between status. You then added more "all" transitions, which exist in all status to take you to another status. So, of course you are going to find several transitions out of each status - you've created new ones. It sounds like you didn't think "all" was a…
-
That's because "approvers" is a list of users. The question you're asking if translated into plain English is "Are Dave, Alice and Bob greater than three?". Which is not a valid question. You will need to set up a sensible question - either create a JQL function that will count up the number when given a field name, or a…
-
No, it's just called "backlog" now instead. Probably because no-one ever called it "plan", just "backlog"