Comments
-
love coasters too or at least used to. age has made my tolerance a bit challenge for any of the newer looping coasters.
-
Unfortunately my answer remains the same. If you want you can reach out to Atlassian Support to get their input and/or provide feedback. If you do, please reference this thread so they can catch up on the conversation. There may be suggestions already open for similar requests. But unsure how a solution would be…
-
No at least not to my knowledge. I deal with this very thing where my internal customer go to the portal and are not logged in and see my public project and they choose to open a ticket there rather than login and get access to the right project. It is an ongoing trading exercise.
-
Duplicate post This is working as designed. Since the 20 public projects are just that “public”, anyone that goes to the portal will see those projects. There is no concept of “blacklist” that would exclude specific customers from public projects.
-
It seems to be working as designed to me. ”anyone can send a request without logging in” = public project which means anyone that stumbles across the URL will see the project and can create a request at which tie they get added as a customer (self-signup like). you cannot restrict the customer for a public project. Anyone…
-
you will need an addon for this, e.g. Scriptrunner, Power Scripts, Automation for Jira, etc.
-
Some things to check... unlikely but - I want to be sure the SLA is in fact associated with the project where the issue with the still running SLA exists is there any other condition where the timer starts other than create that could result in restarting the timer? Have you tried initiating a comment for customer to check…
-
You must ensure that each project’s Customers are aligned with your needs. In other words go to Customers and inspect to ensure the users listed are those that should have access to the given project. If you use Organizations be sure to inspect there as well.
-
Why not use quick filters to focus on each Assignee individually?
-
I’m trying to understand what you are stating here. I will capture what should be happening and why in hopes that we move closer to an answer for you. you have two projects: A-Private and B-Public if anyone goes to the main portal UR” they will all see B-Public but only those individuals that are listed as Customers of…
-
Natively you cannot. I would check the Marketplace for possible addon solutions.
-
When sharing dashboards you need to share all filters used in the gadgets in addition to sharing the dashboard itself.
-
in words only. that is, there is zero functionality tied to the 'type' of link. These are only there as a means of labeling the link. Note that I do not have these same link types or haven't noticed them.
-
ok so you are speaking of specific reports under the Reports section of a JSD project which is rather limited in the ability to customize. I generally accomplish my needs by using a Dashboard that is leveraging a filter as I previously mentioned. This allows me to provide more detailed info.
-
got it. so in short - "none" is treated as an acceptable value. So let me rewind a bit to your question of how to remove "none". Is the location field a custom field you added or is it a field that is associated w/ an addon? I expect the later because you mention in the original post "...make the "account" Temp plugin…
-
yum pizza.... So the final JQL query that will allow you to achieve your goals will depend on precise requirements but this can get you started. project = myjsdproject AND createdDate > startOfWeek() AND createdDate < now() or... project = myjsdproject AND createdDate > startOfDay() or... project = myjsdproject AND…
-
so is this for Jira or Jira Service Desk? For JSD you can edit notifications under project settings > customer notifications. But I'm guessing you already know that and your question is more involved maybe.
-
if you want to see by sprint then go to Reports and Burnup Report and select your sprint. If you just want to see all issue done on previous sprints you can perform a JQL search, e.g. project = abc and status = done and Sprint in closedSprints()
-
can you share the screenshot of where you are trying to change this? I assume you are trying to enter the new username. does the username show up?
-
Hi Jeremy and welcome to the community. First, I wanted to let you know that the Community is primarily made up of users like yourself and as such we can't really fix anything if it is indeed broken. That asside, are you on Cloud? How are you trying to change the project lead? I assume you are going to project > project…
-
what you could consider is to create a special request type and hide it from the portal. This request type would allow Agents to create a request for the customer using either "Raise a Request" or directly in Jira. You will also want to have a unique issue type to associate the request type to I suspect.
-
Are you on Cloud or Server? I just tried this on my cloud instance and it works fine. You might reach out to Atlassian Support. It is odd that you can add after the fact. I wonder if there is some addon conflicting here, but just a theory.
-
thanks for teaching me something new today Nic! ;-)
-
Eric, first some house keeping. use the "Reply" button to reply to someone in a thread and the "Answer" button to offer an answer to the original question that is different than other answers. Now I suspect that you cannot remove the "none". However, as I think you stated if the user selects "none" they will not be allowed…
-
do you want "none" to be allowed during the transition? Field required views "none" as empty. If you want to allow "none" (seems odd to me if it is required) then you might try "field updated" validator? TBH, I don't know if it would pass on "none" being selected.
-
yes so you are on Software Simplified. I don't use this solution often but would refer you to this article - using-the-simplified-workflow IMO, SSWF seems like an early run at what has evolved into NG but it still exists today.
-
you could use Automation to 'follow' the status from the development issue. That is, when the "linked issues" transition from say To Do to In Progress then the JSD issue could be transitioned to In Progress and a comment added to the customer. This does mean that you need to align statuses in JSD to the extent desired. If…
-
well if you are in "Board settings" then it isn't NG because there are no board settings to be had. Are you in the Columns view? You don't "add" statuses there you "map" them. Can you send screen shot. There is also the notion of a project using Software Simplified workflow where you add statuses by adding columns. So many…
-
i'm guessing you are using Next-gen project in the cloud maybe? If so, in NG by adding columns you are in effect adding statuses. If you are on Classic projects you would go to board settings and map existing statuses to columns and you can add columns there too. If you need new statuses you would add them to your workflow.
-
Use Automation. when - comment added if - comment by customer if - status = Done/resolved then - transition back to open or other status