Comments
-
@Devin Canterberryalso can you check Board Settings > Columns to observe statues-column mapping. Was it working previously and just stopped?
-
@Meg Holbrook, couldn't agree more. I don't want to taste anything that is tasting be in return. ;-)
-
Yes. If you have admin permissions you can edit the workflow, select the transition and expose it to the portal.
-
i would assume that the sla timer is not showing in the view issue screen as well but certainly that should be checked since it is but an assumption. :-)
-
Just an opinion so feel free to cast it aside. I'm not a huge fan of using WIP limits. I have used in very rare occasions but generally I find it best to have the teams learn their abilities and manage their WIP. Certainly column constraints can be useful to illustrate 'too much' or 'too little'.
-
when you create a sprint in a scrum board Jira assigns a value, which is not always intuitive BTW. At that point you can, if you wish, select the sprint value via the dropdown. Rarely do I do this, opting instead for using the backlog board to drag-drop issues into a sprint.
-
@Audra Bonacki, can you try to add " ASC" to the end of your query?
-
-
as a test - you could add 'reopened' transition (if you have it) to the Start then reopen one that does not have SLA and see if it then starts.
-
The only thing I can think of at this point is an addon conflict and I would go thru and start disabling one at a time to find the culprit. Unfortunately it doesn't sound like you can cause the problem on-demand so it might be worth trying to find the recipe that will allow you to reproduce the issue so you have a…
-
actually i use Rank for that purpose and it works well. as long as you order the filter by rank it then becomes a stacked rank list. Each assignee can then know which to work next as it will be on the top of their list.
-
looks like it. probably a good idea as there have been quite a number of good changes since 7.4. Please consider accepting the answer to close this issue if it achieved your goal.
-
unfortunately you cannot configure it OOTB which is most unfortunate. I'm sure there is a suggestion for this and you can search for it and vote/comment on it. The way it works is by the number, e.g. the largest number in the set is blue... Two options: * download and change the source code - not likely worth it * look at…
-
What version are you on? Epics appears to have been introduced to server version 7.5.
-
Do you have any addons installed? I have seen this occur when there are compatibility issues with addons. the other thing to look at is the history and transition tabs of two issues, one that displays and one that does not. Look for any differences that might explain the cause. I’m assuming they all go thru the initial…
-
The first question based upon images - Are all issues of typed Incident? Your SLA is only set up for that issuetype.
-
I don’t know what you mean by “switch” nor activate panel really. Are you just trying to set up a Kanban board? Can you give us more details with where you are stuck?
-
well I love just about all food save one - Liver. But I guess if we evaporated that into the cosmos it might have a profound impact on life expectancy. YIKES!
-
one of my favorite books! In fact my ssid at home is StinkyCheeseMan. :-)
-
@seanredmond1, given this is a public Community I have removed the SEN you posted. As for your issue i'm not able to assist personally. Possibly someone else will be able to but you may need to reach out to Atlassian Support.
-
Create a board and a quick filter. the quick filter should be something like - assignee is Empty. For the component piece you can either use quick filters or you can add the component to the card. For the share piece - Go to the board settings and General and edit the share
-
I expect it is how the workflow is designed. Normally approvals happen at creation of the issue. Since the issue has already gone thru that 'transition' then the approvers are not notified. I would suggest you create a transition that mimics the creations, e.g. a transition from the 'approval' status back to the 'approval'…
-
It becomes complicated if the issues are of different issue types as that can translate to different workflows so the selected issues may not be allowed into the same status/column. You can see this behavior when you use bulk move feature w/ multiple issuetypes/workflows. The bulk move will only do one type at a time. Now…
-
Or better yet... if you aren’t specifically trying to exclude issue types then simplify to... project =FFF
-
sure sounds like a bug. is this cloud or server? I expect you will need Atlassian support to assist w/ this one and suggest opening a ticket. @Gabriel Senna any further thoughts on this.
-
"licensing team"? is that your internal IT group or are you speaking of Atlassian? I'm not sure what you mean by private but the portal access can be configured under Customer Permissions.
-
I meant do not share. You mention “can’t license” - to be clear customers do not require a license. They are free in JSD. Only agents are licensed.
-
@marcus test, what do you mean by filter by due date? If you wish to simple order ASC or DSC by due date you don’t need a plug-in to achieve that.
-
@Bojana Vasic, have you made sure that in fact you don’t have two custom fields by that name? If there are two fields then I expect they are both exposed to the portal.
-
@Jayalakshmi TVNR, assume you are on cloud and not server. It was changed to drop down in cloud. There is no configuration to go back to buttons.