Comments
-
seem to work fine for me
-
?? "deboning" report? where are you finding this report?
-
For a full explanation of the Velocity report I would refer you to the documentation: Commitment: The gray bar for each sprint shows the total estimate of all issues in the sprint when it begins. After the sprint has started, any stories added to the sprint, or any changes made to estimates, will not be included in this…
-
I think you mean 'delete the issue's duedate'. You simply delete the value in the field and hit return.
-
Note if you have loaded your own icons it could be that there is an issue gaining access to where they have been saved. That has happened to me in the past. If you are unsure you can check the path... Settings > Issues > Priorities > Edit the Normal icon and check the path
-
There is no field of type counter. You could consider creating a custom field called say "Instances" or whatever of type number field and simply increment it manually. I was thinking that you might be able to hijack the "Vote" field as it is like a counter. However, after thinking about you only get one click per user so…
-
@ianvanzyl, I'm not absolutely sure I'm following you but let's see if we can figure this out. First, I assume you want to make these fields required on the Portal so that your customers are required to enter a value for them when creating a ticket. Assuming this is correct, read on... It sounds like maybe you made these…
-
Basically you can build a new screen or edit the one that is currently being used (but avoid this is you are sharing the screen w/ other projects). Then edit the WF, double-click the transition and assign the screen to that transition. This will ensure that the screen pops up w/ the desired fields and you can make those…
-
yep. you need to set the "Epic Status" to DONE which is different than the Status in the workflow. Yes, I know this is confusing but it is what it is. To set the Epic Status to DONE go into the edit screen and look for "Epic Status" if you do not see then you need to add it to the edit screen. I think you may be able to do…
-
understood. the current validator requires that the user log time when transitioning. For this to work you need to have the transition screen actually present 'log time'. I think what you want is to ensure that time spent is not empty if the user transitions? If so try the following on the transition: * Use Condition *…
-
@Ron Jacob, lets get a bit more detail * has this ever worked? * can you share an image of the board settings > Columns screen? * if you run the filter in the search issues what statuses are your issues in?
-
can u share screenshot of your validator? at what point in the process did the time get logged?
-
It does not appear as if that is possible. At least I have not found a way of doing so and I did not find any suggestion that has been created to provide this config option.
-
There is not a 'higher order' than Epic except maybe Project. While you could certainly create an IssueType called Feature it cannot act as a container for epics. IMO, epics should be a child of a feature. In my experience, Epics are typically many months or certainly many-many weeks long. If you have a feature that is…
-
Try... project = crew and description ~"HPI"
-
Yep. We created a "Hold" status (category of To Do) and my team transitions from "Waiting for Support" to "Hold" if we are waiting on 3rd-party, e.g. something ordered, etc. We Pause the SLA on that status. Then they transition back to WFS (in progress category) when unblocked which should restart the SLA
-
@jb, your question really is better suited as a "discussion" and if you are interested in actually having a discussion on the UX I would recommend creating a new Discussion on the topic. Not sure having the discussion in this thread will be effective.
-
Agree w/ Lara here and w/ Atlassian. While changing the Properties are not for the feint of heart there are times where they can be quite useful. The challenge comes in getting the property to work the way you want exactly, remembering that it is there and being able to remember to investigate that area when…
-
here are a couple of methods I would consider: * use the Outbound email built into Jira to send an email to all member of Jira Service Desk Team and request that they send you an email indicating whether they need or not. * use the Application access to find the list of users then use this filter resolution changed by…
-
create a filter in the Search for issues Advanced screen something like below.... project = abc and sprint in (sprint1, sprint2, sprint3...) ----- here you list the sprints you want to include. of project = abc and Sprint in closedSprints() ----- if you want all closed sprints then just export.
-
@Susan S., i would recommend you ask this on a new thread. This is a rather old thread and your issue seems rather unique and deserves fresh attention.
-
This would be a nice feature but you can't accomplish w/ the OOTB pie gadget. I would recommend looking at an addon. Here is a link to Marketplace addons for charts for Jira Cloud version.
-
the system admin would be able to query all issues on all projects w/o having to have permissions set up at project level.
-
if you don't have permissions then you will not be able to accomplish. I would suggest that you have your system admin run it for you. if you need this ongoing then have them save and share the filter. then build a dashboard and use the "Filter counts" gadget.
-
there is only the burndown in the gadget list.
-
if you are speaking of what the customer sees when creating an issue you can remove the fields as follows: project > Project settings > Request Types > Edit fields and remove the fields not needed you will need to do this for every request type that has the fields NOTE: the fields were likely placed there for a reason,…
-
if you just want to know the total number of issues in your instance you could JQL with something like --- project is not EMPTY
-
you must have a Create screen and that is where it needs to be removed from. At least that is my guess.
-
@Daniel Eads {unmonitored account}, i'm not sure that JQL will work. Often you can end up w/ the CRT as empty, e.g. email channel. The only way I have found to show all JSD issues is to use project in (a,b,c...) and ensure you get all JSD projects. It is unfortunate that you cannot search by "project type" but that is meta…
-
you need to add the custom fields to the Create screen. Go into your project > project settings > screens. Find the screen used for Create, edit and add your fields at the bottom and feel free to rearrange them.