Comments
-
When editing a Confluence page click on the "+" icon at the end of the toolbar on right. Select Other Macros. Choose your gadget.
-
Is your last column "Done" or similar? Do you need those issue to be displayed there? If it isn't a SW project where you are using the "Release" feature to get those issues off the board consider the following options: * edit the filter to only display the done issues w/in that last say 30d or whatever * edit the workflow…
-
There are a number of issues already open related to the ESC key behavior. ESC key related issues
-
This has been asked a number of times w/in the Community. A quick search will expose the discussions. Here is one but there are others. Bottomline: Cloud - you cannot accomplish Server - you can use a proxy
-
If you click on the Organization under the Customers menu and use "Add Customer" it will simply move them if they exist in 'root'. I wish you could simply have a check box where you could move multiple from root but it doesn't exist. :-(
-
yes. sorry. wasn't paying attention. :-( For JSD you could opt for Components, Custom field or Labels. Depending on your specific requirement I would suggest Components. As a Jira system field it has some built in capabilities that often make it a better choice. You won't be able to do this directly from w/in the Queues…
-
You can flag issues. Please see this article. Cloud - Flagging an issue Server (7.8) - Flagging an issue
-
@Rita Mewing, you may want to open a separate question that captures the cloud issue you are experiencing unless it is precisely the same. You may wish to include a screenshot as well.
-
@Sajesh, please have a look at the following: https://confluence.atlassian.com/adminjiracloud/exporting-issues-776636787.html
-
quickest way... * type "gg" * enter "dashboard" * select "Shared dashboards" * find the dashboard and click on ellipsis another way... * click Jira icon in top right * click on Dashboard * select manage dashboards at the bottom of list * find the dashboard and click on ellipsis
-
given that detail I can only suggest that the Agents will need to change the type based upon say the summary or description. In other words, I believe this is going to need to be managed by your Agents not employees that are Customers.
-
@Amy Dudek, just create a Request Type (call it "Feature") and hide from portal under the request types screen.
-
and if you want all of the stories/tasks under the epics included in your export try this modified one (issuetype = Epic or "Epic Link" is not empty) and project = XYZ
-
Agree. I will say that I do have odd renderings from time to time on my cloud instance. Generally it clears with cache or another browser but occasionally it hangs around for the day. I have never seen this specific scenario though. @Mario Ustar, if you are not on a 10 user license and this persists then I would reach out…
-
@Don Reab, that is odd. have you check another browser just for grins? I'm able to rearrange just fine. Note, i don't have a "handle". I just grab the queue and move.
-
You need to create filters that are specific to the individual. then use those filters to create you dashboard. Example: Fred's Open Issues: assignee = fred.flinstone and status != done Fred's Completed Work: assignee = fred.flinstone and status = done With that said, one thing to consider is creating a dashboard called…
-
one thing I ran into in the early days was that I had password expiration turned on for the account. 90d later it stopped. Took me a few minutes of head scratching to realize the error of my ways.
-
It’s because you and your stories are more important than others! sorry, Couldn’t resist. Are you sure others are defaulting to bottom? My experience has new issues going to the top.
-
My second guess is an add on. Do you have any?
-
This looks to be a browser issue. Can you try an alternate browser and/or clear cache.
-
No. But you could coordinate with the admin monthly to enable them disable.
-
click the Jira icon in the top left this should present you with the following in the sidebar: * Dashboards * Projects * Issues * Settings
-
and if you simply want to hide them from view just have a quick filter "Hide Done"
-
@Alexander Ragnarsson, so you are saying that you enter time in the original estimate field and it actually isn’t ‘accepted’ right. That is, after you enter a value and then save the changes the field is blank? I assume you are entering the time in the Edit issue screen? If not can you test that? I would be interested if…
-
Have you considered simply creating a custom field for internal use of categorization?
-
if you are not on a "10 user starter" license then I suggest opening a support case w/ Atlassian Customer Support. If you are on this limited license then the Community is your only recourse unfortunately. Unsure if anyone here will be able to assist w/ your situation but we shall see.
-
Given this I think I would have a project per customer and Components for products. This will allow you to easily keep reporting straight. You still could keep a single project if you wanted but it isn’t as clean and flexible. SIngle project: * Project = Consulting * Components = Web Design, System, Solution, etc *…
-
The purpose of having different organizations is so that customers in one org cannot share with customers in another org. If you want all customers to be able to share with each other then they need to go into a single org. But that would be an abnormal use case.
-
From CSV? Issues > search for issues > ellipses > import from CSV
-
@Ronnie Poulsen, let me start w/ a question. Are the products you support shared across customers? That is, does product A apply to Customer A and Customer B? If the products are shared then my recommendation (FWIW) would be to stick w/ products as projects and leverage a Customer field to distinguish between customers. If…