Comments
-
Oh, by the way, I create a second board that does not have the restriction of the reporter part so I can see all issues. But then I only share that filter with the Administrators group. :-)
-
Hi Lucasz - yes, it is very much because it is a Next gen project. One other solution is to create a board with a filter that includes something like this: project = "Internal Service Desk" AND reporter = currentUser() See if that works for you. It will not prevent the user from seeing issues if they were to do a search by…
-
Also will migrate with Cloud Files add-on if using that. :-)
-
Hi Lukasz, I would like the user as the Reporter on the issue and then restrict the project with issue level security where the Reporter = currentUser I hope that helps.
-
Hi Andrea - Welcome to the Community! You can do as Bill suggests above, but you can also display 3 fields for each card using the card layout under Board Settings. So you can show Status as one of the fields to be able to quickly see which Status the issue is currently in.
-
No, you have to start typing the name. :-(
-
There's an open issue that Atlassian is working to allow fields to be added to the left side. Last status I saw was that it was coming soon.
-
Hi Ben, Take a look at this link - I think it will answer this for you. https://community.atlassian.com/t5/Jira-Core-questions/Configure-the-new-Jira-issue-view/qaq-p/681056
-
Hi Michiel - can you edit the issue to change any other values? If not, it probably means that based on the Permission Scheme you do not have permissions to edit issues on that project. Start by checking the permission scheme.
-
Sorry - did not realize that Server was different. Doesn't make a lot of sense.
-
Hi Daniel - Welcome to the Community! The Story issue type will follow the path of your workflow attached to that issue type. So, it should eventually end up in a Done status. Can you verify the workflow it is using? (Click on the View Workflow link below the status in the "old" JIRA Issue view).
-
Nope, it still showed the first Column that has a status in it, so Open would still show up. Sorry, just doesn't look like you can get rid of it.
-
I guess, theoretically, you could create a column in the board settings as the first column and put no status in there. The column won't show up on your board since no status is in it. But it might keep Open from showing up in the Backlog. Will experiment with that myself and see what happens.
-
In the Backlog view, it always shows the statuses in the Backlog section of the board along with the first Column on the main board. In your case, that is the Open column. That is why you see those in the bottom section of your Backlog page.
-
Ah, I see. Yes, not sure how they determine that order - might possibly be by field ID. Lots of inconsistencies across the administration within JIRA as to order of things - some alphabetical, some now.
-
Hi Anda, I duplicated your scenario but I only see the Copy of Books and Training board associated with the project that is listed in the location. See the screenshot. The Copy board is in both projects of JMF2 and Books and Training. But it is only connect with the location for JMF2 project. In the screenshot it shows…
-
Hi Boris, Why not create an admin user or "old projects user" or something to that effect. And then import them under that user?
-
Agree with Jack - usually change to a permission scheme with only Admin access. And even then, I also change the Project Category to Archived or something like that so it doesn't appear in any of my reporting.
-
That is correct - you would need to have two permission schemes. Or possibly handle it based on project roles and have different people in different role.
-
Hey Michael - You should be able to arrange the fields in order on your screen. Are they not in the same order?
-
Hey Jeff, Have you looked at the Permission scheme to make sure that they or their role does not have access to Time Logging?
-
Agree with Bill - if you just want to see Backlog tickets in the Backlog space, you should only have the Backlog status there.
-
Great - glad you found a potential solution!
-
Hi Mari, I am very sorry - I misunderstood your original question. I am not away of a way to filter out the list or projects. Nor can you add fields to the project record itself for software projects. You might be using Service Desk or another type of project.
-
I would start with one piece at a time and then add to it until something disappears. For example, "Epic Link" = ABC-123 and see if anything comes up. Then add project, etc.
-
Hi Mari, The filter will probably look something like: project type in (New, Updated) and Subtype in ("New partner chanel", "new structure", etc.) and partner in ("Partner 1", Partner 2", etc.) and Status in ("Open", "Inactive", etc.) Is that what you are looking for?
-
Hey Alfie - Welcome to the Community! We use the JMWE add-on to create a new ticket as it transitions to a different status. Works great!
-
Oddly enough, some of our teams have implemented what we call a "triage" process. We added three new statuses between Backlog and Backlog Pullable. They are Reviewed - Not Ready, Reviewed - Incomplete, Reviewed - Ready. So when an issue comes into the backlog, it stays until it can be reviewed. Once reviewed, it moves into…
-
Hi XianKe - Welcome to the Community! Try clicking on the magnifying glass on the left side nav bar. Then at the bottom of the newly displayed list, click on the Advanced search for Boards. That will take you to a list of all boards where you can do a search. I hope that helps!
-
Hi Randall, The way we operate is that all ideas/requests/stories/tasks, etc. get created and placed in the backlog. That gives us a central location and visibility into all requested/desired work. As a part of refining (use whatever term you like) the backlog, all requirements are placed on the issue that was discussed…